Get desktop application:
View/edit binary Protocol Buffers messages
ConsumerOffsetInfo contains information about consumer offsets.
Used in:
offset_info contains information about the offsets for a given topic.
consumer_group is the consumer group name that this ConsumerGroupInfo is being reported for.
committedOffset is the last committed offset for this consumer group. This may be -1 if there are no consumer offsets checkpointed.
uncommitted_count is the number of messages for this topic-partition that has yet to be committed. On worker rebalance or restart, this is the number of message that will be received. This is calculated as highwatermark - committedOffset - 1.
Request and Response objects. ConsumerOffsetInfoRequest is the request that will be made to POST /getConsumerOffsetInfo in aakafkaoffsetmgmt.
ConsumerOffsetInfoResponse is the response that will be returned on POST /getConsumerOffsetInfo in aakafkaoffsetmgmt.
ConsumerOffsetStore is an enum for place where consumer offsets are stored.
Used in: , , , ,
consumer self manage their kafka offset store
DLQMetadata contains metadata from the original kafka message used in messaging-consumer-go lib and /data/messaging/clients:consumer The metadata will be encoded and decoded when sending or receiving messages from the DLQ cluster in order to present the library user a seamless logical topic.
retry_count is an incrementing value denoting the number of times a message has been redelivered. It will be 0 on first delivery.
topic is the original kafka topic the message was received on. This is analogous to the logical topic name.
partition is the original kafka partition the message was received on.
offset is the record offset of the original message in the original topic-partition.
timestamp_ns is the original record timestamp of the original message.
data is a byte buffer for storing arbitrary information. This is useful if the Kafka Broker version used is < 0.11 and hence Kafka native record headers (KAFKA-4208) are unavailable so the DLQ metadata must be stored in the record Key or Value.
timeout_count is an incrementing value denoting the number of times a message has been redelivered due to timeout. It will be 0 on first delivery.
Used in:
group_name is the consumer group id
the offset store (KAFAK10, KAFKA8) that the group is shown
GroupSubscriptionRequest contains the parameters for making a group subscription curl call to offset management
cluster is the kafka cluster.
group is the consumer group
GroupSubscriptionResponse contains the group subscription response object returned by rest endpoint of offset management.
cluster is the kafka cluster.
group is the consumer group
topics is an array of topics subscribed by the group
ListGroupRequest contains the parameters for making a listGroup curl call to offset management
cluster is the kafka cluster.
ListGroupResponse contains listGroup response object returned by rest endpoint of offset management.
an array of groupAndOffsetStore instances
Used in:
low watermark = high watermark or offset not in [lowwatermark, highwatermark] for all partition
no offset snapshots to utilize for mapping
existing dst offsets > src mapped offsets for all partitions
no error
OffsetInfo contains information about offsets.
Used in:
cluster is the kafka cluster.
topic is the kafka topic.
partition is the kafka partition.
low_watermark is the offset of the first message that is currently available on the broker.
high_watermark is the offset of the next message produced to the broker. note: the offset of the latest mesage available on the broker is highwatermark - 1.
src kloak cluster
dst kloak cluster
consumer group name on the src cluster
consumer group name on the dst cluster
offset store from the src cluster
offset store from the dst cluster
the topic to migrate.
user provided partition offsets from the src cluster.
disable checking existing offsets on the dst cluster and simply use the translated values from offset snapshot
OffsetSyncResponse contains the offset sync response returned by rest endpoint of offset management. the purpose is to make the user aware of what offset values are being used at src and dst cluster respectively.
consumer group name from the srcCluster
consumer group name from the dstCluster
topic to sync
consumer kafka version from the srcCluster
consumer kafka version from the dstCluster
mapping status indicates the offset state from the src cluster and snapshots
partition offset_infos from the src cluster
partition offsets from the dst cluster
partition and its associated offset info
Used in: ,
by default UNSET commit offset value is -1. should be explictly set in the builder since proto default value is 0
partition beginning offset
partition ending offset
message lags between offset and highWatermark