Skip to content

DOCSP-48323: Causal consistency feedback #224

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.

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

Closed
Changes from all commits
Commits
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: 5 additions & 1 deletion source/write/transactions.txt
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,10 @@ operations. For example, if you perform a series of operations where
one operation logically depends on the result of another, any subsequent
reads reflect the dependent relationship.

.. note::

A client session enables causal consistency even if it does not perform a transaction.

The following table describes the guarantees that causally
consistent sessions provide:

Expand Down Expand Up @@ -90,7 +94,7 @@ consistent sessions provide:
``delete_one()`` to delete the retrieved document, the driver runs the find
operation first.

In a causally consistent session, MongoDB ensures a causal relationship between the
In a causally consistent session, MongoDB guarantees causal consistency between only the
following operations:

- Read operations that have a ``majority`` read concern
Expand Down
Loading