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

3.4: Mention stricter createIndexes validation in release notes

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.0
    • Component/s: Rel Notes
    • Labels:
    • # Replies:
      3
    • Last comment by Customer:
      true
    • Story Points:
      0.25
    • Sprint:
      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

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              james.wahlin James Wahlin
              Participants:
              Last commenter:
              Jonathan Dahl
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                3 years, 41 weeks, 5 days ago
                Date of 1st Reply: