[SERVER-75357] Consider moving static checks in rename collection into the command itself Created: 27/Mar/23  Updated: 29/Oct/23  Resolved: 06/Jul/23

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

Type: Improvement Priority: Major - P3
Reporter: Wenqin Ye Assignee: Pau Baldillou Salse (Inactive)
Resolution: Fixed Votes: 0
Labels: neweng, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-78653 Remove renameCollection static checks... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-07-10
Participants:

 Description   

We should move the static checks in the `RenameCollectionCoordinator`  into the renameCollection command itself. This is so that the checks can be performed before any threads are even scheduled or before any locks are even taken.

Alternatively, we could consider adding something to the command infrastructure where there is some static checking phase.



 Comments   
Comment by Githook User [ 06/Jul/23 ]

Author:

{'name': 'Pau Baldillou Salse', 'email': 'pau.baldillou-salse@mongodb.com', 'username': ''}

Message: SERVER-75357 Move static checks to command implementation.
Branch: master
https://github.com/mongodb/mongo/commit/ab528541db1986b3d2d1d7609b40db311b2706ac

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