Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
None
-
None
Description
Description
Description:
When we define a new flag for restoring existing UUIDs, it will need to be added to the docs.
Engineering Ticket Description:
In MongoDB 3.6, collections can be created in two ways:
- using create, they are assigned a new UUID
- using applyOps, they can be created with a pre-existing UUID (details TBD)
However, creating with a UUID will require special permissions. We need to create a command line flag to opt into reusing existing UUIDs when restoring and to use the appropriate mechanism if set. The implications of doing so or not doing so will need to be documented.
Update: from
TOOLS-1862epic, the desired behavior is as follows:
- Add a --preserveUUIDs flag
- With --preserveUUIDs, have the following behaviors:
- Require the --drop flag or abort
- Require collection metadata to contain UUID info or abort
- Require the destination to be in FCV 3.6 or abort (MUST check both ways that FCV could appear)
- Create collections with the desired UUID with a synthesized applyOps command
- Follow procedure in
SERVER-31906for creating admin.system.version with a given UUID- Apply oplog without removing UUIDs
Scope of changes
Impact to Other Docs
MVP (Work and Date)
Resources (Scope or Design Docs, Invision, etc.)
Attachments
Issue Links
- documents
-
TOOLS-1817 Add 'preserveUUIDs' flag to restore collections with existing UUIDS
-
- Closed
-
- is duplicated by
-
DOCS-12437 Docs for TOOLS-1862: Revise UUID support for MongoDB 4.0
-
- Closed
-