[SERVER-53106] Preserve chunks entries upon sharded collection rename Created: 30/Nov/20 Updated: 06/Dec/22 Resolved: 08/Feb/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: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | PM-1965-Milestone-0-Metadata-Format | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
Once The removeCollMetadataFromConfig method must be modified to take that into account. A possible solution would be to pass a boolean deleteChunks - instead of the collection uuid - expecting the method to retrieve the uuid from the config.collection entry (if exists) before proceed with the deletion. |
| Comments |
| Comment by Githook User [ 08/Feb/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |