Skip to content

DRIVERS-3480 Clarify that the operationTime MUST save rule excludes unacknowledged writes #1938

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
GromNaN wants to merge 1 commit into
base: master
Choose a base branch
from
Open

DRIVERS-3480 Clarify that the operationTime MUST save rule excludes unacknowledged writes #1938

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 6 additions & 3 deletions source/causal-consistency/causal-consistency.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -196,9 +196,9 @@ started with `causalConsistency = true` then all operations using that session w

There are no new server commands related to causal consistency. Instead, causal consistency is implemented by:

1. Saving the `operationTime` returned by 3.6+ servers for all operations in a property of the `ClientSession` object.
The server reports the `operationTime` whether the operation succeeded or not and drivers MUST save the
`operationTime` in the `ClientSession` whether the operation succeeded or not.
1. Saving the `operationTime` returned by 3.6+ servers for all acknowledged operations in a property of the
`ClientSession` object. The server reports the `operationTime` whether the operation succeeded or not, and drivers
MUST save the `operationTime` in the `ClientSession` whether the operation succeeded or not.
2. Passing that `operationTime` in the `afterClusterTime` field of the `readConcern` field for subsequent causally
consistent read operations (for all commands that support a `readConcern`)
3. Gossiping clusterTime (described in the Driver Session Specification)
Expand Down Expand Up @@ -403,6 +403,9 @@ resolving many discussions of spec details. A final reference implementation mus

## Changelog

- 2026-05-13: Clarify that the "MUST save operationTime" rule applies only to acknowledged operations; unacknowledged
writes receive no server response and do not update the session's `operationTime`.

- 2024-02-08: Migrated from reStructuredText to Markdown.

- 2022-11-11: Require `causalConsistency=false` for implicit sessions.
Expand Down
Loading