package amphi.proto

Get desktop application:
View/edit binary Protocol Buffers messages

The service definitions for pixels-amphi.

• rpc TranspileSql (TranspileSqlRequest, TranspileSqlResponse)

  amphi.proto:33

  message TranspileSqlRequest

  amphi.proto:50

  begin request/response definition for rpc services

  • optional RequestHeader header = 1

  • string sqlStatement = 2

  • string fromDialect = 3

  • string toDialect = 4

  message TranspileSqlResponse

  amphi.proto:57

  • optional ResponseHeader header = 1

  • string sqlTranspiled = 2

• rpc TrinoQuery (TrinoQueryRequest, TrinoQueryResponse)

  amphi.proto:34

  message TrinoQueryRequest

  amphi.proto:62

  • optional RequestHeader header = 1

  • string trinoUrl = 2

  • int32 trinoPort = 3

  • string catalog = 4

  • string schema = 5

  • string sqlQuery = 6

  message TrinoQueryResponse

  amphi.proto:71

  • optional ResponseHeader header = 1

  • string queryResult = 2

• rpc CoordinateQuery (CoordinateQueryRequest, CoordinateQueryResponse)

  amphi.proto:35

  message CoordinateQueryRequest

  amphi.proto:76

  • optional RequestHeader header = 1

  • string peerName = 2

  • string schema = 3

  • string sqlStatement = 4

  message CoordinateQueryResponse

  amphi.proto:83

  • optional ResponseHeader header = 1

  • bool inCloud = 2

    to be executed on peer side if false

  • string queryResult = 3

    empty if inCloud is false

header

Used in: CoordinateQueryRequest, TranspileSqlRequest, TrinoQueryRequest

• string token = 1

Used in: CoordinateQueryResponse, TranspileSqlResponse, TrinoQueryResponse

• string token = 1

• int32 errorCode = 2

  errorCode == 0 means success

• string errorMsg = 3

  empty if errorCode == 0