Distributed / multi-document transaction support#327
Open
hatspencer wants to merge 14 commits into
Open
Conversation
hatspencer
marked this pull request as draft
November 22, 2025 17:20
hatspencer
marked this pull request as ready for review
November 24, 2025 08:12
- propagate session also for reads - extend tests and examples
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation:
MongoDB supports distributed transactions since version 4.2, and this has been also available on the driver level for a while. The goal of this PR is to add API support for such distributed / multi document transactions.
Related issues: #242, #158
The newly defined MongoSession is a wrapper implementation around MongoClient but with the added control for start/commit/abort.
Usage examples:
MongoClient#executeTransaction()- compose and execute the provided future in transaction, commit on success, abort on failure automatically using handlers.MongoClient#startSession()- allows for manual control of commit / abort.By default, the underlying session is started with a transaction and closed automatically after commit or abort. The client session's behaviour can be changed by passing a ClientSessionOptions instance. For example: