[SERVER-76107] Allow to use snapshotReadConcern in queryOnce Created: 14/Apr/23 Updated: 25/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
queryOnce() has an invariant here invalidating the usage of kSnapshotReadConcern. while this is not the case of runAggregation. We should decide which of the two is correct and unify the behaviors |
| Comments |
| Comment by Louis Williams [ 19/Sep/23 ] |
|
tommaso.tocci@mongodb.com I'm moving this to StorEx because we want to improve the internal read API here. |