[SERVER-52747] Implement rename collection functionality on resharding recipient Created: 10/Nov/20  Updated: 29/Oct/23  Resolved: 18/Nov/20

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

Type: Task Priority: Major - P3
Reporter: Blake Oler Assignee: Alexander Taskov (Inactive)
Resolution: Fixed Votes: 0
Labels: PM-234-M2, PM-234-T-lifecycle
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-52931 [Resharding] Verify, in the reshardin... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-11-30
Participants:

 Description   

This functionality will call the rename command (or some internal function that exists inside that chain of calls that command would start) here.

This ticket does not involve taking care of any interaction with the DonorStateMachine, assuming that a donor/recipient exists on the same shard.

Also investigate the best way to test this – consider that renaming a collection is already tested in unit test code, and if there seems to be nothing particularly special about this rename, create a ticket to verify the behavior in jstests once functionality has been completed up to and through rename.



 Comments   
Comment by Max Hirschhorn [ 18/Nov/20 ]

Author:

{'name': 'Alex Taskov', 'email': 'alex.taskov@mongodb.com', 'username': 'alextaskov'}

Message: SERVER-52747 Implement rename collection functionality on
resharding recipient
Branch: master
https://github.com/mongodb/mongo/commit/dc5601ee3eb22d48723aa21978423a56db81e7e5

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