Summary

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

Auto embedding in Atlas Vector Search requires new feature support - to be able to create vector search indexes with new quantization and numDimensions fields (in the already existing type:autoEmbed field) via language drivers. The new feature will be released on Atlas on April 15 2026.

Required changes: Builder Support and Type Support

Syntax - https://docs.google.com/document/d/13Q-T50m9TM791HZy6AgxOazbo_CWXHAaATg9hYtqZEc/edit?tab=t.0#heading=h.kjikha3v63vm

Motivation

Who is the affected end user?

Atlas Search Developers

How does this affect the end user?

Developers of statically typed languages won't be able to programmatically create their Automated embedding vector search indexes with fields numDimensions and Quantization.

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 not be able to use advanced features like quantization and numDimensions in 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.

Is this issue urgent?

Committed Roadmap item release on April 15 2026

Is this ticket required by a downstream team?

Compass

Is this ticket only for tests?

Functional impact

Acceptance Criteria

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