Details
-
New Feature
-
Status: Closed
-
Critical - P2
-
Resolution: Fixed
-
None
-
Needed
-
Docs should describe how the tool attempts to recover from legacy options, including any options which will be dropped on restore.
-
v4.2
Description
The fix in TOOLS-2379 for old indexes relies on applyOps, which isn't allowed by the MongoDB Atlas shared tier proxy. To address this, mongorestore should ensure that only valid, supported index options are sent. A white list of options may be found in index_descriptor.h (though not all appear to be documented options).
Open question: should this behavior require a flag? Or should it be a fallback only if the initial creation errors? The goal either way should be to allow someone to use a modern mongorestore to restore a legacy dump to a legacy server.
Attachments
Issue Links
- backported by
-
TOOLS-2655 [v4.2] Strip unsupported legacy index options
-
- Closed
-
- is depended on by
-
-
- Closed
-
- is documented by
-
DOCS-13285 Docs for TOOLS-2412: Strip unsupported legacy index options
-
- Closed
-