Package com.linkedin.venice.kafka.protocol
package com.linkedin.venice.kafka.protocol
-
ClassesClassDescriptionControlMessage payloads contain metadata about the stream of data, for validation and debuggability purposes.Delete payloads contain fields related to replication metadata of the record.This ControlMessage is sent per partition by each offline incremental push job, once per partition, at the end of a incremental pushThis ControlMessage is sent once per partition, at the end of a bulk load, after all of the data producers come online.This ControlMessage is sent at least once per partition per producer.Put payloads contain a record value, and information on how to deserialize it.This ControlMessage is sent by the Controller, once per partition, after the EndOfPush ControlMessage, in Hybrid Stores that ingest from both offline and nearline sources.This ControlMessage is sent per partition by each offline incremental push job, once per partition, at the beginning of a incremental push.This ControlMessage is sent once per partition, at the beginning of a bulk load, before any of the data producers come online.This ControlMessage is sent at least once per partition per producer.This ControlMessage is sent by the Controller, once per partition; it will only be used in leader/follower state transition model; this control message will indicate the leader to switch to a new source topic and start consuming from offset with a specific timestamp.Partial update operation, which merges the update value with the existing value.This controlMessage is written to the real-time topic by the controller or to the store-version topic by the current version's leader server.