Skip to content

DRIVERS-3274 Send afterClusterTime on writes in causally-consistent sessions. #1930

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

Merged
dariakp merged 15 commits into from
May 29, 2026
Merged

DRIVERS-3274 Send afterClusterTime on writes in causally-consistent sessions. #1930

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
15 commits
Select commit Hold shift + click to select a range
ec0b2df
DRIVERS-3274 Send afterClusterTime on writes in causally-consistent s…
matthewdale Apr 29, 2026
1163992
Update the spec to cover all read and write commands. Add a clientBul…
matthewdale May 4, 2026
a66b592
Remove unnecessary minServerVersion and redundant prose test. Add bul…
matthewdale May 5, 2026
2994ef4
Expect DDL operations to send afterClusterTime.
matthewdale May 6, 2026
c4c9860
Explicitly forbid 'level' in 'readConcern' for writes. Fix transactio…
matthewdale May 7, 2026
51c4920
Replace findOne with find for the initial operation.
matthewdale May 7, 2026
10bb34b
Writes in transactions don't require afterClusterTime.
matthewdale May 7, 2026
c5b9d04
Require afterClusterTime on writes not in a transaction.
matthewdale May 7, 2026
c3033c4
Remove confusing note about commands supporting readConcern in Read W…
matthewdale May 8, 2026
32f3817
Make sure there are no collection name conflicts in createCollection …
matthewdale May 8, 2026
fa869a3
Correct test descrption in causal-consistency-clientBulkWrite.yml
matthewdale May 8, 2026
ddb6137
Update Causal Consistency test JSON.
matthewdale May 11, 2026
d855b40
Separate the section in Read Concern that describes afterClusterTime …
matthewdale May 27, 2026
89c60b1
Update source/read-write-concern/read-write-concern.md
rozza May 28, 2026
8ab62d6
Add a unified spec test for dropDatabase and for the first write in a…
matthewdale May 29, 2026
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
6 changes: 3 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 @@ -200,7 +200,7 @@ There are no new server commands related to causal consistency. Instead, causal
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`)
consistent read and write operations (for all commands that support a `readConcern`)
Comment thread
rozza marked this conversation as resolved.
3. Gossiping clusterTime (described in the Driver Session Specification)

## Server Command Responses
Expand Down Expand Up @@ -230,10 +230,10 @@ standalone node are causally consistent automatically because there is only one
When connected to a deployment that supports cluster times the command response also includes a field called
`$clusterTime` that drivers MUST use to gossip the cluster time. See the Sessions Specification for details.

## Causally consistent read commands
## Causally consistent read and write commands

For causal consistency the driver MUST send the `operationTime` saved in the `ClientSession` as the value of the
`afterClusterTime` field of the `readConcern` field:
`afterClusterTime` field of the `readConcern` field for read and write commands:

```typescript
{
Expand Down
Loading
Loading