Module vitess_grpc::vtgate

source ·

Modules

  • Nested message and enum types in Session.

Structs

  • CloseSessionRequest is the payload to CloseSession.
  • CloseSessionResponse is the returned value from CloseSession.
  • ExecuteBatchRequest is the payload to ExecuteBatch.
  • ExecuteBatchResponse is the returned value from ExecuteBatch.
  • ExecuteRequest is the payload to Execute.
  • ExecuteResponse is the returned value from Execute.
  • PrepareData keeps the prepared statement and other information related for execution of it.
  • PrepareRequest is the payload to Prepare.
  • PrepareResponse is the returned value from Prepare.
  • ReadAfterWrite contains information regarding gtid set and timeout Also if the gtid information needs to be passed to client.
  • ResolveTransactionRequest is the payload to ResolveTransaction.
  • ResolveTransactionResponse is the returned value from Rollback.
  • Session objects are exchanged like cookies through various calls to VTGate. The behavior differs between V2 & V3 APIs. V3 APIs are Execute, ExecuteBatch and StreamExecute. All other APIs are V2. For the V3 APIs, the session must be sent with every call to Execute or ExecuteBatch. For the V2 APIs, Begin does not accept a session. It instead returns a brand new one with in_transaction set to true. After a call to Commit or Rollback, the session can be discarded. If you’re not in a transaction, Session is an optional parameter for the V2 APIs.
  • StreamExecuteRequest is the payload to StreamExecute.
  • StreamExecuteResponse is the returned value from StreamExecute. The session is currently not returned because StreamExecute is not expected to modify it.
  • VStreamRequest is the payload for VStream.
  • VStreamResponse is streamed by VStream.

Enums

  • CommitOrder is used to designate which of the ShardSessions get used for transactions.
  • TransactionMode controls the execution of distributed transaction across multiple shards.