-
Type:
Spec Change
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Component/s: Causal Consistency
-
None
-
Needed
Summary
The general rule stated drivers "MUST save the operationTime whether the operation succeeded or not", while the "Unacknowledged writes" section stated the operationTime is not updated because no response is received. These appeared contradictory. Clarify that the MUST applies only to acknowledged operations.
Motivation
Who is the affected end user?
Driver authors implementing causal consistency.
Is this issue urgent?
No.
Is this ticket only for tests?
No — spec text clarification.
Acceptance Criteria
PR merged: https://github.com/mongodb/specifications/pull/1938
- related to
-
DRIVERS-3487 Spec analysis: causal-consistency — missing tests, ambiguities, inconsistencies
-
- Backlog
-
- split to
-
CDRIVER-6333 Clarify that the operationTime MUST save rule excludes unacknowledged writes
-
- Blocked
-
-
CSHARP-6046 Clarify that the operationTime MUST save rule excludes unacknowledged writes
-
- Blocked
-
-
CXX-3495 Clarify that the operationTime MUST save rule excludes unacknowledged writes
-
- Blocked
-
-
GODRIVER-3911 Clarify that the operationTime MUST save rule excludes unacknowledged writes
-
- Blocked
-
-
JAVA-6205 Clarify that the operationTime MUST save rule excludes unacknowledged writes
-
- Blocked
-
-
NODE-7585 Clarify that the operationTime MUST save rule excludes unacknowledged writes
-
- Blocked
-
-
PHPLIB-1853 Clarify that the operationTime MUST save rule excludes unacknowledged writes
-
- Blocked
-
-
PYTHON-5828 Clarify that the operationTime MUST save rule excludes unacknowledged writes
-
- Blocked
-
-
RUBY-3880 Clarify that the operationTime MUST save rule excludes unacknowledged writes
-
- Blocked
-
-
RUST-2428 Clarify that the operationTime MUST save rule excludes unacknowledged writes
-
- Blocked
-