[SERVER-53418] Rename preconditions for sharded collections Created: 17/Dec/20  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

Sprint: Sharding 2020-12-28, Sharding 2021-01-11, Sharding 2021-01-25
Participants:

 Description   

As part of the rename flow for sharded collections, the db primary shard should check for the following conditions to be met before starting the rename process:

  • Check that `dropTarget` is true if the destination collection already exists
  • Check that no tags exist for the destination collection

If any of those conditions is not respected, the rename command should fail.



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

Author:

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

Message: SERVER-53418 Rename preconditions for sharded collections
Branch: master
https://github.com/mongodb/mongo/commit/136d56daf7206d20679c49b34c080d3842c2dce5

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