[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: |
|
||||||||
| 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: |