Auto embedding Vector search

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Unresolved
    • Priority: Critical - P2
    • None
    • Component/s: None
    • None
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      CDRIVER-6129 Blocked
      CXX-3374 Blocked
      CSHARP-5763 Blocked
      GODRIVER-3680 Blocked
      JAVA-5988 Blocked
      NODE-7245 Blocked
      PYTHON-5619 Blocked
      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 Blocked GODRIVER-3680 Blocked JAVA-5988 Blocked NODE-7245 Blocked PYTHON-5619 Blocked 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 Atlas Vector Search Public preview is scheduled for Jan 30 2026, and 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.

      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 Atlas 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 Atlas Vector Search indexes. Alternatively, they can use Atlas UI / Admin API / JSON editor 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 feature is expected to roll out by Jan 30 2026 for Public Preview across all Atlas clusters. There is a likelihood of announcing the public preview in .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

      Support for new query parameters and index configurations as specified in the syntax doc - https://docs.google.com/document/d/13Q-T50m9TM791HZy6AgxOazbo_CWXHAaATg9hYtqZEc/edit?tab=t.0#heading=h.kjikha3v63vm

            Assignee:
            Unassigned
            Reporter:
            Prakul Agarwal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: