-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Catalog
-
None
-
Storage Execution
-
(copied to CRM)
While implementing SERVER-52539, I noticed that it's possible to create invalid index entries. For example, we can pass {key: {a: 1}, dropDups: "this should be a bool but it's a string"} to createIndexes, and create an invalid entry, which is then returned by listIndexes.
After SERVER-52539, createIndexes will be much stricter at the command-parsing layer. However, perhaps we should consider more validation at the catalog layer as well.
- is related to
-
SERVER-74305 APIStrict validation is not performed for fields in 'indexes' array in createIndex command
- Backlog
-
SERVER-26287 createIndexes should confirm that index options are valid in respect to the underlying collection
- Closed
-
SERVER-53739 Validate all createIndexes options
- Closed
-
SERVER-54712 createIndexes permits weights for non-text indexes
- Closed
-
SERVER-52539 Specify input/output to createIndexes command in IDL
- Closed
- related to
-
SERVER-49224 Improve validation of index spec fields
- Closed