[DOCS-9049] 3.4: Mention stricter createIndexes validation in release notes Created: 29/Sep/16  Updated: 28/Oct/16  Resolved: 28/Oct/16

Status: Closed
Project: Documentation
Component/s: Rel Notes
Affects Version/s: None
Fix Version/s: 3.4.0

Type: Improvement Priority: Critical - P2
Reporter: James Wahlin Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: bite-sized
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-7038 Document new restrictions on index ke... Closed
related to DOCS-9204 3.4 release notes compatibility chang... Closed
is related to SERVER-26659 Only apply stricter index key pattern... Closed
is related to SERVER-769 Validate top-level & index spec field... Closed
Participants:
Days since reply: 7 years, 15 weeks, 5 days ago
Story Points: 0.25

 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}]});



 Comments   
Comment by Githook User [ 28/Oct/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-9049 DOCS-7038 3.4 index specification validation
Branch: master
https://github.com/mongodb/docs/commit/3d50078e3e6246ae5f6d557aa13946a7a8184924

Comment by David Storch [ 25/Oct/16 ]

We no longer need to mention the scenario described by asya above. Due to the changes made under SERVER-26659, no user action will be required on upgrade to clean up bad index key patterns. This is because the additional key pattern validation now only applies to new v:2 indexes. Let me know if you have any questions about this.

Comment by James Wahlin [ 29/Sep/16 ]

This change should be mentioned in the "breaking changes" section of the release notes.

Generated at Thu Feb 08 07:57:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.