Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-87792

The 'originalSpec' option to the createIndexes command's index specification is under-constrained

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Catalog
    • Storage Execution
    • ALL

      The originalSpec is validated as an index specification but there's no requirement the originalSpec has any association with the actual index definition. Some examples of validation which are absent and may lead to problematic behavior if assumptions change in the future include:

      • The originalSpec option can be specified for a non-timeseries collection.
      • The originalSpec option can be an index specification with its own nested originalSpec option.
      • The index specification's name and version are not required to match originalSpec.name or originalSpec.v, respectively.
      • The originalSpec option can refer to an index specification which will be returned by listIndexes yet errors when provided to createIndexes.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: