Details
-
Task
-
Resolution: Done
-
Major - P3
-
None
-
None
Description
Description
Added validation of number of arguments for shell functions ensureIndex, createIndex and createIndexes. Arguments handling or functions behaviour is not changed.
Description of Linked Ticket
If a third argument is passed to the ensureIndex() with valid options, then the behavior is to ignore the third argument instead of an error. So for example, if I execute the following
db.myColl.ensureIndex( { my_date: 1}, {expireAfterSeconds: 2678400},{background: true, sparse: true } )
|
the third argument which is critical to the purpose of this index build is completely ignored and the index is built in the foreground with no sparse option. This can lead to catastrophic events if myColl is very large and foreground index was not a choice. Can this be fixed so a user is not punished for accidentally passing the critical options as a third argument in the index build? The version we tried this is 3.2.9
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- documents
-
SERVER-26726 Check number of arguments for createIndex() and throw error if more than two arguments
-
- Closed
-