[SERVER-53737] Check for sharded collections in renameCollectionLegacy Created: 13/Jan/21  Updated: 13/Jan/21  Resolved: 13/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: Done Votes: 0
Labels: PM-1965-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-51758 Support shard-local rename of sharded... Closed
Sprint: Sharding 2021-01-25
Participants:

 Description   

Rename collection code is currently checking if collections are sharded in several parts, sometimes relying on skipSourceCollectionShardedCheck to decide whether to skip such checks.

Ideally, the check can be performed just once in the new command path, before ending up in the actual rename collection code.



 Comments   
Comment by Githook User [ 13/Jan/21 ]

Author:

{'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}

Message: SERVER-53737 Check for sharded collections in renameCollectionLegacy
Branch: master
https://github.com/mongodb/mongo/commit/a2e32913f7f6321b4cf293066703e867391db431

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