-
Type:
Bug
-
Resolution: Won't Do
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Indexes
-
None
-
Environment:OS:
node.js / npm versions:
Additional info:
-
Not Needed
-
Developer Tools
Problem Statement/Rationale
What is going wrong? What action would you like the Engineering team to take?
There is no validation to verify that numPartitions is an invalid parent level field for vector search indexes. The Atlas UI properly warns against this as an invalid parameter, but Compass allows you to create an index.
The index rebuilt fine, no warnings, no errors. But after the rebuild the "numPartitions" parameter was missing from the index definition. This might create a confusing customer experience
Please be sure to attach relevant logs with any sensitive data redacted.
How to retrieve logs for: Compass; Shell
Steps to Reproduce
How could an engineer replicate the issue you’re reporting?
Try and create a vectorSearch-type index via Compass with the numPartitions field specified.
Expected Results
What do you expect to happen?
A warning or error signifying that this is an invalid field
Actual Results
What do you observe is happening?
The index is allowed to be built, with the numPartitions field not appearing anywhere within it
Additional Notes
Any additional information that may be useful to include.