Expand description
Nested message and enum types in StreamReadMessage.
Modules§
- commit_
offset_ request - Nested message and enum types in
CommitOffsetRequest. - commit_
offset_ response - Nested message and enum types in
CommitOffsetResponse. - from_
client - Nested message and enum types in
FromClient. - from_
server - Nested message and enum types in
FromServer. - init_
request - Nested message and enum types in
InitRequest. - read_
response - Nested message and enum types in
ReadResponse.
Structs§
- Commit
Offset Request - Signal for server that client processed some read data.
- Commit
Offset Response - Acknowledgement for commits.
- Direct
Read Ack - Signal for server that client has finished direct reading. Server should not send a response to the command.
- EndPartition
Session - Signal from server that client has finished reading the partition and all messages have been read. Once a partition has been finished no further messages will ever arrive to that partition. This command is a hint to the client to commit offsets, after which the child partitions will be balanced independently in different reading sessions. Unlike StopPartitionSessionRequest, the client does not have to close the reading session. Client should not send a response to the command.
- From
Client - Client-server message for read session. Contains one of: InitRequest - handshake request. ReadRequest - request for data. CommitOffsetRequest - request for commit of some read data. PartitionSessionStatusRequest - request for session status UpdateTokenRequest - request to update auth token DirectReadAck - client signals it has finished direct reading from the partition node.
- From
Server - Server-client message for read session. Contains one of: InitResponse - handshake response from server. ReadResponse - portion of data. CommitOffsetResponse - acknowledgment for commit. PartitionSessionStatusResponse - server response with partition session status. UpdateTokenResponse - acknowledgment of token update.
- Init
Request - Handshake request.
- Init
Response - Handshake response.
- Partition
Session - Within a StreamRead session delivered messages are separated by partition. Reads from a single partition are represented by a partition session.
- Partition
Session Status Request - Partition
Session Status Response - Response to status request.
- Read
Request - Message that represents client readiness for receiving more data.
- Read
Response - Data read.
- Start
Partition Session Request - Command from server to create and start a partition session. Client must respond with StartPartitionSessionResponse when ready to receive data from this partition.
- Start
Partition Session Response - Signal for server that client is ready to recive data for partition.
- Stop
Partition Session Request - Command from server to stop and destroy concrete partition session.
- Stop
Partition Session Response - Signal for server that client finished working with this partition. Must be sent only after corresponding StopPartitionSessionRequest from server. Server will give this partition to other read session only after StopPartitionSessionResponse signal.
- Update
Partition Session - Command from server to notify about a partition session update. Client should not send a response to the command.