-
Type: Task
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Go Drivers
Context
Usage of causal consistency mechanics that do not rely on implicit behavior can be confusing for users, as drivers MUST NOT attempt to validate the supplied operationTime. For example, the following error will be propagated by the server if a user passes around the OperationTime from a ClientSession without also passing along its corresponding ClusterTime:
readConcern afterClusterTime value must not be greater than the current clusterTime
Definition of done
Document the details for explicit CC mechanics defined in the specifications for SessionOptions.CausalConsistency, Session.AdvanceClusterTime, and Session.AdvanceOperationTime.
- related to
-
DRIVERS-2860 Introduce new API for starting a causally consistent session from the timestamps of another operation or client session
- Backlog