Driver support for new syntax in Auto embedding in Community Vector search

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Unresolved
    • Priority: Critical - P2
    • None
    • Component/s: None
    • Needed
    • Hide

      Summary of necessary driver changes

      • Drivers should be able to test manually against some build that has the correct API
      • Integration tests can be deferred to follow up work to complete once a CI-compatible server is available with this feature (file a follow-up DRIVERS ticket and block on corresponding upstream work)

      Commits for syncing spec/prose tests
      (and/or refer to an existing language POC if needed)

      • None

      Context for other referenced/linked tickets

      • AutoEmbedding Syntax Document
      Show
      Summary of necessary driver changes Drivers should be able to test manually against some build that has the correct API Integration tests can be deferred to follow up work to complete once a CI-compatible server is available with this feature (file a follow-up DRIVERS ticket and block on corresponding upstream work) Commits for syncing spec/prose tests (and/or refer to an existing language POC if needed) None Context for other referenced/linked tickets AutoEmbedding Syntax Document https://docs.google.com/document/d/13Q-T50m9TM791HZy6AgxOazbo_CWXHAaATg9hYtqZEc/edit?tab=t.0#heading=h.kjikha3v63vm
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      CDRIVER-6129 Blocked
      CXX-3374 Blocked
      CSHARP-5763 Done 3.6.0
      GODRIVER-3680 Works as Designed
      JAVA-5988 In Progress
      NODE-7245 Works as Designed
      PYTHON-5619 Works as Designed
      PHPLIB-1734 Blocked
      RUBY-3718 Blocked
      RUST-2296 Blocked
      $i18n.getText("admin.common.words.show")
      #scriptField, #scriptField *{ border: 1px solid black; } #scriptField{ border-collapse: collapse; } #scriptField td { text-align: center; /* Center-align text in table cells */ } #scriptField td.key { text-align: left; /* Left-align text in the Key column */ } #scriptField a { text-decoration: none; /* Remove underlines from links */ border: none; /* Remove border from links */ } /* Add green background color to cells with FixVersion */ #scriptField td.hasFixVersion { background-color: #00FF00; /* Green color code */ } #scriptField td.willNotDo { background-color: #FF0000; /* Red color code */ } /* Center-align the first row headers */ #scriptField th { text-align: center; } Key Status/Resolution FixVersion CDRIVER-6129 Blocked CXX-3374 Blocked CSHARP-5763 Done 3.6.0 GODRIVER-3680 Works as Designed JAVA-5988 In Progress NODE-7245 Works as Designed PYTHON-5619 Works as Designed PHPLIB-1734 Blocked RUBY-3718 Blocked RUST-2296 Blocked

      Summary

      What is the problem or use case, what are we trying to achieve?

      Auto embedding in Community Vector Search requires new feature support for Python, JS, Java, C#, GoLang drivers. This feature provides a 1-click AI semantic search powered by Voyage AI models. Community release scheduled for Jan 15 2026, to be announced in SF .Local. 
      PD - https://docs.google.com/document/d/1xYiRFjZKCsJNjD-jiAJS7qAW8M2r9TYfVj5cCJ-CozY/edit?tab=t.0

      Required changes: Builder Support and Type Support

      Motivation

      Who is the affected end user?

      Atlas Search Developers

      How does this affect the end user?

      Developers won't be able to use the new Community Vector Search feature to programmatically create/edit their vector search indexes, and be able to query them.

      How likely is it that this problem or use case will occur?

      Main case for the target users

      If the problem does occur, what are the consequences and how severe are they?

      Users would be blocked to adopt Auto embedding Vector Search indexes. Alternatively, they can use compass, etc to configure their indexes, which is acceptable in the short term for testing but not for production use cases. For querying they would be blocked which is a bigger concern.

      Is this issue urgent?

      This is a big announcement at .Local SF on Jan 15 2026.

      Is this ticket required by a downstream team?

      Compass

      Is this ticket only for tests?

      Functional impact

      Acceptance Criteria

        1. Drivers should be able to test manually against some build that has the correct API
        2. Integration tests can be deferred to follow up work to complete once a CI-compatible server is available with this feature (file a follow-up DRIVERS ticket and block on corresponding upstream work)
        3. File a single DOCSP ticket (DOCSP-56077) to update the index reference page with new examples

            Assignee:
            Casey Clements
            Reporter:
            Prakul Agarwal
            Jib Adegunloye Jib Adegunloye
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: