Mongorestore should ignore InvalidOptions error if unknown option is documentDB specific

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Tools and Replicator
    • 234

      In TOOLS-3598 we see that in early June 2024 Amazon added an option to collections in DocumentDB that is not supported by Mongorestore storageEngine

      In a workflow that uses mongodump to create an export and then tries to restore the export into a cluster, the export will be successfully created but the restore will fail. Instead, we should check for the InvalidOptions error and check to see if the problematic option(s) are DocumentDB specific (based on a list of known options). If they are DocumentDB specific, then we should strip these options and retry the command.

      Currently the list of known options is ["storageEngine"]

      The impact of this is that dump/restore workflows from documentDB to mongoDB will not fail in this way.

            Assignee:
            Unassigned
            Reporter:
            Rohan Sharan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: