Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
Used in:
Used in:
An emtpy message. Since CQL RPC server bypasses protobuf to handle requests and responses but RPC context expects the request and response messages to be present, we set up an empty message inside RPC context to satisfy it.
(message has no fields)
Sent as response when is_error == true.
TODO: Make code required?
Specific error identifier.
These codes have all been inherited from Hadoop's RPC mechanism.
Used in:
Non-fatal RPC errors. Connection should be left open for future RPC calls. ------------------------------------------------------------ The application generated an error status. See the message field for more details.
The specified method was not valid.
The specified service was not valid.
The server is overloaded - the client should try again shortly.
The request parameter was not parseable or was missing required fields.
FATAL_* errors indicate that the client should shut down the connection. ------------------------------------------------------------ The RPC server is already shutting down.
Could not deserialize RPC request.
IPC Layer version mismatch.
Auth failed.
Used in:
Used in:
Used in:
Service name for the RPC layer. The client created a proxy with this service name. Example: yb.rpc_test.CalculatorService
Name of the RPC method.
The header for the RPC request frame.
Used in:
A sequence number that is sent back in the Response. Hadoop specifies a uint32 and casts it to a signed int. That is counterintuitive, so we use an int32 instead. Allowed values (inherited from Hadoop): 0 through INT32_MAX: Regular RPC call IDs. -2: Invalid call ID. -3: Connection context call ID. -33: SASL negotiation call ID.
RPC method being invoked. Not used for "connection setup" calls.
Propagate the timeout as specified by the user. Note that, since there is some transit time between the client and server, if you wait exactly this amount of time and then respond, you are likely to cause a timeout on the client.
If this is set, then this is an error response and the response message will be of type ErrorStatusPB instead of the expected response type.
Byte offsets for side cars in the main body of the response message. These offsets are counted AFTER the message header, i.e., offset 0 is the first byte after the bytes for this protobuf.
Used in:
Used in:
Used in:
Used in:
Used in:
Connection is still being negotiated.
Connection is active.
Used in: