[SERVER-70799] Remove ShardVersion::IGNORED() Created: 24/Oct/22 Updated: 29/Oct/23 Resolved: 13/Mar/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 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20 |
| Participants: |
| Description |
|
ShardVersion::IGNORED() is used for multi-writes that are not part of a transaction. These writes are broadcast to all shards with ShardVersion::INGORED() which tells the shards to ignore the shard versioning checks. As part of the global indexes project, we are adding an index version to the shard version. We have decided that instead of creating a ShardVersion::IGNORED() and an CollectionIndexes::IGNORED(), we will send ShardVersion(ChunkVersion::IGNORED(), indexVersion) where indexVersion is a valid version for multi updates. This ticket is to remove ShardVersion::IGNORED() and make sure that the usages of this are attaching and handling the index version correctly |
| Comments |
| Comment by Githook User [ 13/Mar/23 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |