[SERVER-85370] Move rename precondition checks away from generic utility API Created: 18/Jan/24  Updated: 22/Jan/24  Resolved: 22/Jan/24

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc0

Type: Task Priority: Major - P3
Reporter: Antonio Fuschetto Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-84243 Separate Shard-Role Catalog Cache and... In Progress
Backwards Compatibility: Fully Compatible
Sprint: CAR Team 2024-01-22
Participants:

 Description   

The validation of the rename preconditions on the from/to namespaces is implemented by checkRenamePreconditions and checkDbPrimariesOnTheSameShard, which are functions exposed by a generic utility API.

Since these functions are based on some assumptions (e.g., DDL lock, the shard is the primary of source database, etc.) the goal is to move all or some of them into the coordinator of the rename command.



 Comments   
Comment by Githook User [ 19/Jan/24 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-85370 Move rename precondition checks away from generic utility API (#18172)

GitOrigin-RevId: ddcd025fe0febc83e5922cb58fa500236c8a143e
Branch: master
https://github.com/mongodb/mongo/commit/b7d94959c5172c7e34fd9857e6559a8b9366a91b

Generated at Thu Feb 08 06:57:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.