-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding 2020-11-02, Sharding 2020-11-16, Sharding 2020-12-14, Sharding 2020-12-28, Sharding 2021-01-11, Sharding 2021-01-25, Sharding 2021-02-08
As a prerequisite for renaming sharded collections, a shard-local renameCollection within the same database needs to be implemented.
The current logic of renameCollectionWithinDB for RS can potentially be reused, but needs to be complemented in order to support sharded collections.
(RenameCollection preserves the collection uuid, so chunks should be automatically associated to the new collection once SERVER-53106 will be completed)
- depends on
-
SERVER-53737 Check for sharded collections in renameCollectionLegacy
- Closed
- duplicates
-
SERVER-52781 Implement the new rename collection path in `_shardsvrRenameCollection`
- Closed
- is depended on by
-
SERVER-52781 Implement the new rename collection path in `_shardsvrRenameCollection`
- Closed