Transaction commands

Transaction context

Use the driver's transaction API to maintain matching session and transaction metadata. Read isolation follows the shared read-concern rules.

commitTransaction and abortTransaction

Using the airline example dataset, start a transaction with a read and commit it. The session helper maintains matching lsid and txnNumber values:

const bookingsSession = db.getMongo().startSession({ causalConsistency: false })
const bookingsDb = bookingsSession.getDatabase("bookings")
bookingsSession.startTransaction()
bookingsDb.flights.findOne({ route_no: "PG0101" })
bookingsSession.commitTransaction()
bookingsSession.endSession()

Use bookingsSession.abortTransaction() instead of commitTransaction() to abort. The helpers do not return a raw command document; the wire handlers return ok: 1 on success. A missing or nonexistent active transaction produces NoSuchTransaction; committing an already committed transaction is handled as an idempotent retry.

The handlers do not implement per-command writeConcern policies, maxCommitTimeMS, or recovery-token coordination.

Source: gateway processor/transaction.rs and requests/common_fields.rs.