com.youtube.vitess.proto.vtgate
caller_id identifies the caller. This is the effective caller ID, set by the application to further identify the caller.
session carries the current transaction data. It is returned by Begin. Do not fill it in if outside of a transaction.
queries is a list of query and bind variables to execute.
tablet_type is the type of tablets that these queries is targeted to.
as_transaction will execute the queries in this batch in a single transaction per shard, created for this purpose. (this can be seen as adding a 'begin' before and 'commit' after the queries). Only makes sense if tablet_type is master. If set, the Session is ignored.
keyspace to target the queries to.
options
as_transaction will execute the queries in this batch in a single transaction per shard, created for this purpose.
as_transaction will execute the queries in this batch in a single transaction per shard, created for this purpose. (this can be seen as adding a 'begin' before and 'commit' after the queries). Only makes sense if tablet_type is master. If set, the Session is ignored.
caller_id identifies the caller.
caller_id identifies the caller. This is the effective caller ID, set by the application to further identify the caller.
keyspace to target the queries to.
options
queries is a list of query and bind variables to execute.
session carries the current transaction data.
session carries the current transaction data. It is returned by Begin. Do not fill it in if outside of a transaction.
tablet_type is the type of tablets that these queries is targeted to.
(Since version 0.6.0) Use toPMessage
(Since version 0.6.0) Use getField that accepts a ScalaPB descriptor and returns PValue
ExecuteBatchRequest is the payload to ExecuteBatch.
caller_id identifies the caller. This is the effective caller ID, set by the application to further identify the caller.
session carries the current transaction data. It is returned by Begin. Do not fill it in if outside of a transaction.
queries is a list of query and bind variables to execute.
tablet_type is the type of tablets that these queries is targeted to.
as_transaction will execute the queries in this batch in a single transaction per shard, created for this purpose. (this can be seen as adding a 'begin' before and 'commit' after the queries). Only makes sense if tablet_type is master. If set, the Session is ignored.
keyspace to target the queries to.
options