[DRIVERS-2782] Expose atClusterTime parameter in snapshot sessions Created: 28/Nov/23 Updated: 21/Dec/23 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | Sessions |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kiro Morkos | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Driver Changes: | Needed |
| Quarter: | FY25Q2 |
| Downstream Changes Summary: | Summary of necessary driver changes Commits for syncing spec/prose tests Context for other referenced/linked tickets |
| Description |
SummaryThe snapshot session specification states that drivers should store the atClusterTime value in a private field, but there are many instances where an application may want to set/access the value. MotivationWho is the affected end user?Users of a driver that would like to take advantage of snapshot reads. How does this affect the end user?There are a few snapshot sessions usages that are not possible to do today given the current limitation. e.g.
How likely is it that this problem or use case will occur?Main path? Edge case? If the problem does occur, what are the consequences and how severe are they?Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete? Is this issue urgent?Does this ticket have a required timeline? What is it? Is this ticket required by a downstream team?It is required for Device Sync. In the meantime, we had to expose this field in our fork of the go driver: https://github.com/mongodb-forks/mongo-go-driver/commit/5cd00b584fc0e0019f20822274214110b2f55ab2 Is this ticket only for tests?No Acceptance Criteria
|