[SERVER-69770] Enforce the required lock mode in the CollectionShardingRuntime API Created: 16/Sep/22 Updated: 29/Oct/23 Resolved: 03/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Daniel Gomez Ferro |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2144-Cleanup | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2022-12-26, Execution Team 2023-01-09 |
| Participants: |
| Description |
|
We should make the type of lock required be enforced by the API. One idea is to have two acquisition methods:
|
| Comments |
| Comment by Githook User [ 18/Jan/23 ] |
|
Author: {'name': 'Daniel Gómez Ferro', 'email': 'daniel.gomezferro@mongodb.com', 'username': 'dgomezferro'}Message: |
| Comment by Githook User [ 03/Jan/23 ] |
|
Author: {'name': 'Daniel Gómez Ferro', 'email': 'daniel.gomezferro@mongodb.com', 'username': 'dgomezferro'}Message: |
| Comment by Antonio Fuschetto [ 16/Sep/22 ] |
|
This makes sense for the DatabaseShardingState as well. |