Details
-
Improvement
-
Status: Closed
-
Critical - P2
-
Resolution: Done
-
None
-
0.25
-
KANBAN BUCKET
Description
Under SERVER-769 we made createIndexes command validation stricter for both top level fields and index specification fields. It may be worth mentioning this in the 3.4 release notes as there may be users whose index creation scripts fail on upgrade due to invalid fields.
Examples of createIndexes command execution that succeed for 3.2 and fail for 3.4:
db.runCommand('createIndexes', {indexes: [{key: {e: 1}, name: 'e_1'}], 'invalidField': 1});
|
db.runCommand('createIndexes', {indexes: [{key: {e: 1}, name: 'e_1', 'v': 2, 'invalidField': 1}]});
|
Attachments
Issue Links
- is related to
-
SERVER-26659 Only apply stricter index key pattern validation to v:2 indexes
-
- Closed
-
-
SERVER-769 Validate top-level & index spec field names for the createIndexes command
-
- Closed
-
