[SERVER-51758] Support shard-local rename of sharded collections Created: 20/Oct/20  Updated: 10/May/22  Resolved: 28/Jan/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Pierlauro Sciarelli
Resolution: Duplicate Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-53737 Check for sharded collections in rena... Closed
is depended on by SERVER-52781 Implement the new rename collection p... Closed
Duplicate
duplicates SERVER-52781 Implement the new rename collection p... Closed
Sprint: 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
Participants:

 Description   

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)



 Comments   
Comment by Pierlauro Sciarelli [ 28/Jan/21 ]

Closing because it's being done in the broader SERVER-52781 work.

Generated at Thu Feb 08 05:26:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.