TransactionOption

The transaction, if not self-conflicting, may be committed a second time after commit succeeds, in the event of a fault

The read version will be committed, and usually will be the latest committed, but might not be the latest committed in the event of a fault or partition

Undocumented

The next write performed on this transaction will not generate a write conflict range. As a result, other transactions which read the key(s) being modified by the next write will not conflict with this transaction. Care needs to be taken when using this option on a transaction that is shared between multiple threads. When setting this option, write conflict ranges will be disabled on the next write operation, regardless of what thread it is on.

Committing this transaction will bypass the normal load balancing across proxies and go directly to the specifically nominated ‘first proxy’.

Undocumented

Reads performed by a transaction will not see any prior mutations that occured in that transaction, instead seeing the value which was in the database at the transaction’s read version. This option may provide a small performance benefit for the client, but also disables a number of client-side optimizations which are beneficial for transactions which tend to read and write the same keys within a single transaction.

Undocumented

Undocumented

Undocumented

Undocumented

Specifies that this transaction should be treated as highest priority and that lower priority transactions should block behind this one. Use is discouraged outside of low-level tools

Specifies that this transaction should be treated as low priority and that default priority transactions should be processed first. Useful for doing batch work simultaneously with latency-sensitive work

This is a write-only transaction which sets the initial configuration. This option is designed for use by database system tools only.

Allows this transaction to read and modify system keys (those that start with the byte 0xFF)

Allows this transaction to read system keys (those that start with the byte 0xFF)

Undocumented

Undocumented

Enables tracing for this transaction and logs results to the client trace logs. Client trace logging must be enabled to get log output.

Set a timeout in milliseconds which, when elapsed, will cause the transaction automatically to be cancelled. Valid parameter values are [0, INT_MAX]. If set to 0, will disable all timeouts. All pending and any future uses of the transaction will throw an exception. The transaction can be used again after it is reset. Like all transaction options, a timeout must be reset after a call to onError. This behavior allows the user to make the timeout dynamic.

Set a maximum number of retries after which additional calls to onError will throw the most recently seen error code. Valid parameter values are [-1, INT_MAX]. If set to -1, will disable the retry limit. Like all transaction options, the retry limit must be reset after a call to onError. This behavior allows the user to make the retry limit dynamic.

Set the maximum amount of backoff delay incurred in the call to onError if the error is retryable. Defaults to 1000 ms. Valid parameter values are [0, INT_MAX]. Like all transaction options, the maximum retry delay must be reset after a call to onError. If the maximum retry delay is less than the current retry delay of the transaction, then the current retry delay will be clamped to the maximum retry delay.

Snapshot read operations will see the results of writes done in the same transaction.

Snapshot read operations will not see the results of writes done in the same transaction.

The transaction can read and write to locked databases, and is resposible for checking that it took the lock.

By default, operations that are performed on a transaction while it is being committed will not only fail themselves, but they will attempt to fail other in-flight operations (such as the commit) as well. This behavior is intended to help developers discover situations where operations could be unintentionally executed after the transaction has been reset. Setting this option removes that protection, causing only the offending operation to fail.

The transaction can read from locked databases.