[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: |
|
||||||||||||||||||||
| 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 |
| Comments |
| Comment by Pierlauro Sciarelli [ 28/Jan/21 ] |
|
Closing because it's being done in the broader |