Details
-
Task
-
Resolution: Fixed
-
Major - P3
-
5.0 Required
-
None
Description
Review/adapt the renameCollection documentation:
- Sharded collections: specify that rename for sharded collections is now allowed (but not between different DBs)
- Resource Locking: this section is currently just valid for plain replica sets
- Exceptions: all the currently listed exception codes don't exist anymore
Attachments
Issue Links
- related to
-
DOCS-13880 Source and target database primary shards should match when renaming unsharded collections
-
- Closed
-