[SERVER-70196] The DocumentSourceMerge should contain a ShardVersion, not a ChunkVersion Created: 04/Oct/22 Updated: 07/Feb/23 Resolved: 07/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | PM-2583-Milestone-3 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Participants: |
| Description |
|
The document source merge contains a chunk version currently. It uses this version in the shardsvr_process_interface to check that the epoch is up to date. In this check, the catalog cache time in store is advanced. Here, we should be using a ShardVersion so that a stale index cache will also be advanced. As part of this ticket, we should either talk to query or request their review to ensure this is behavior is alright. |
| Comments |
| Comment by Allison Easton [ 07/Feb/23 ] |
|
Since the target collection version in the document source merge is only used to check the epoch of the collection, we don't need to store the index version here. |