| Safe Haskell | None |
|---|---|
| Language | Haskell2010 |
Data.Hadoop.Protobuf.Headers
- data UserInformation = UserInformation {}
- data IpcConnectionContext = IpcConnectionContext {
- ctxUserInfo :: Optional 2 (Message UserInformation)
- ctxProtocol :: Optional 3 (Value Text)
- data RpcKind
- data RpcOperation
- data RpcRequestHeader = RpcRequestHeader {
- reqKind :: Optional 1 (Enumeration RpcKind)
- reqOp :: Optional 2 (Enumeration RpcOperation)
- reqCallId :: Required 3 (Value Word32)
- data RpcRequest = RpcRequest {
- reqMethodName :: Required 1 (Value Text)
- reqBytes :: Optional 2 (Value ByteString)
- reqProtocolName :: Required 3 (Value Text)
- reqProtocolVersion :: Required 4 (Value Word64)
- data RpcStatus
- data RpcResponseHeader = RpcResponseHeader {}
Documentation
data UserInformation Source
User information beyond what can be determined as part of the security handshake at connection time (kerberos, tokens, etc)
Constructors
| UserInformation | |
data IpcConnectionContext Source
The connection context is sent as part of the connection establishment. It establishes the context for ALL Rpc calls within the connection.
Constructors
| IpcConnectionContext | |
Fields
| |
Determines the RPC Engine and the serialization of the RPC request.
Constructors
| Builtin | Used for built-in calls by tests |
| Writable | Use WritableRpcEngine |
| ProtocolBuffer | Use ProtobufRpcEngine |
data RpcOperation Source
Constructors
| FinalPacket | The final RPC packet |
| ContinuationPacket | Not implemented yet |
| CloseConnection | Close the RPC connection |
Instances
data RpcRequestHeader Source
Constructors
| RpcRequestHeader | |
Fields
| |
data RpcRequest Source
This message is used for Protobuf RPC Engine. The message is used to marshal a RPC request from RPC client to the RPC server. The response to the RPC call (including errors) are handled as part of the standard RPC response.
Constructors
| RpcRequest | |
Fields
| |
Instances
Success or failure. The reponse header's error detail, exception class name and error message contains further details on the error.
data RpcResponseHeader Source
Note that RPC response header is also used when connection setup fails. (i.e. the response looks like an RPC response with a fake callId)
For v7: - If successfull then the Respose follows after this header - length (4 byte int), followed by the response - If error or fatal - the exception info follow - length (4 byte int) Class name of exception - UTF-8 string - length (4 byte int) Stacktrace - UTF-8 string - if the strings are null then the length is -1
In case of Fatal error then the respose contains the Serverside's IPC version.
Constructors
| RpcResponseHeader | |