Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-9049

3.4: Mention stricter createIndexes validation in release notes

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • 3.4.0
    • Affects Version/s: None
    • Component/s: Rel Notes
    • Labels:
    • 0.25

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

            Assignee:
            kay.kim@mongodb.com Kay Kim (Inactive)
            Reporter:
            james.wahlin@mongodb.com James Wahlin
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:
              7 years, 30 weeks, 3 days ago