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

[TOOLS] Check for duplicate index keys after converting legacy index definitions

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: tools
    • Labels:
      None

      Description

      Description

      Engineering Description
      If a dump has two indexes, {foo: ""} and {foo: 1}, and we restore with --convertLegacyIndexes, then we will get an error: 

      (IndexOptionsConflict) Index with name: foo_1 already exists with a different name

      We could check to see if we have duplicate indexes after legacy index conversion and discard the legacy index, or we could just ignore the error.

      Both options would have the effect of removing the legacy index. This would mean that index hints for that index would no longer work in the restored db.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              Anonymous Anonymous
              Participants:
              Last commenter:
              Andrew Feierabend Andrew Feierabend
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Days since reply:
                51 weeks, 6 days ago