Execute a v10 transaction

Determines the encoded format expected for the query arguments field, and the data field of a successful response.

If set, will act as the minimum snapshot time the query will be executed at. Clients will automatically populate this based on the highest "txn_ts" result value observed of any transaction the client has processed.

Enable or disable typechecking of the query before evaluation. Defaults to the value of the "typechecked" on the database configuration.

If true, unconditionally run the query as strictly serialized. This affects read-only transactions, as transactions which write will already be strictly serialized.

If true, include query performance hints in the summary field of the response.

A client-specified query timeout in milliseconds.

The maximum number of times a transaction is allowed to retry due to concurrent contention failure before an error is returned.

A string-encoded set of caller-determined tags which identify the request. Provided back via logging and the query response body. The format is a list of key value pairs, like so. - foo=bar - foo=bar,baz=blah Each key and each value may only contain the characters [a-zA-Z0-9_]. These are also valid tags. - foo_bar=baz - foo3=1234,5=6 All of these are invalid. - foo bar=3 // no spaces - foo=bar, // no trailing commas - foo==bar // too many = Each key must be less than or equal to 40 bytes. Each value must be less than or equal to 80 bytes. There can only be a maximum of 25 key/value pairs total. Additionally, the entire header cannot be more than 3000 bytes.