[SERVER-72889] Add checks to shard version constructor to ensure chunk version and index version belong to same collection Created: 17/Jan/23 Updated: 29/Oct/23 Resolved: 22/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-2583-Milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06 |
| Participants: |
| Description |
|
The constructor of the ShardVersion takes in a ChunkVersion and a CollectionIndexes. We should either pass in a ChunkManager and a CollectionIndexes or additionally pass in the UUID with the chunk version so that we can add in a check in the constructor that the UUID from the chunk version and index version match. Note that we won't be able to check this if the index version is boost::none, but we should add the checks for all initialized chunk versions. |
| Comments |
| Comment by Githook User [ 21/Feb/23 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |