-
Type: Improvement
-
Resolution: Won't Do
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Internal Code
-
None
-
Storage Execution
-
(copied to CRM)
As we add internal-use collections such as the sessions collection or a future transactions collection, tools like mongodump will wind up dumping these collections.
If internal-use collection can be annotated in collection options with some flag that tools can detect, then tools can omit such collections from dump operations without needing users to remember to specific exclusions or for the tools to maintain a blacklist of collections to omit.
- is depended on by
-
SERVER-5972 Cannot drop system.js collection
- Closed
-
SERVER-5955 Forbid renaming system collections
- Closed
- is related to
-
SERVER-27147 Do not initial sync data written with setReplicatedWrites(false)
- Closed
-
TOOLS-1797 mongodump must skip collections used for sessions
- Closed
-
SERVER-23546 Collection::requiresIdIndex may be incomplete
- Closed
-
TOOLS-1636 mongodump fails when capped collection position lost
- Waiting (Blocked)
- related to
-
TOOLS-2222 Mongodump should ignore config.transactions and config.transaction_coordinators
- Closed
-
SERVER-67147 Allow system.profile to be dropped when profiling is enabled
- Closed