The request for
Required. The session in which the DML
statements should be performed.
Required. The transaction to use. Must be a
To protect against replays, single-use
transactions are not supported. The caller must
either supply an existing transaction ID or
begin a new transaction.
Required. The list of statements to execute in this batch.
Statements are executed serially, such that the effects of
statement i are visible to statement i+1. Each
statement must be a DML statement. Execution stops at the
first failed statement; the remaining statements are not
Callers must provide at least one statement.
Required. A per-transaction sequence number
used to identify this request. This field makes
each request idempotent such that if the request
is received multiple times, at most one will
The sequence number must be monotonically
increasing within the transaction. If a request
arrives for the first time with an out-of-order
sequence number, the transaction may be aborted.
Replays of previously handled requests will
yield the same response as the first execution.