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

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

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • Server_Docs_20231030
    • None
    • tools
    • 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

        Activity

          People

            Unassigned Unassigned
            Anonymous Anonymous
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              1 year, 14 weeks, 2 days ago