[ https://issues.apache.org/jira/browse/KAFKA-10026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kowshik Prakasam resolved KAFKA-10026. -------------------------------------- Resolution: Duplicate Duplicate of KAFKA-10027 > KIP-584: Implement read path for versioning scheme for features > --------------------------------------------------------------- > > Key: KAFKA-10026 > URL: https://issues.apache.org/jira/browse/KAFKA-10026 > Project: Kafka > Issue Type: New Feature > Reporter: Kowshik Prakasam > Priority: Major > > Goal is to implement various classes and integration for the read path of the > feature versioning system > ([KIP-584|https://cwiki.apache.org/confluence/display/KAFKA/KIP-584%3A+Versioning+scheme+for+features]). > The ultimate plan is that the cluster-wide *finalized* features information > is going to be stored in ZK under the node {{/feature}}. The read path > implemented in this PR is centered around reading this *finalized* features > information from ZK, and, processing it inside the Broker. > > Here is a summary of what's needed for this Jira (a lot of it is *new* > classes): > * A facility is provided in the broker to declare it's supported features, > and advertise it's supported features via it's own {{BrokerIdZNode}} under a > {{features}} key. > * A facility is provided in the broker to listen to and propagate > cluster-wide *finalized* feature changes from ZK. > * When new *finalized* features are read from ZK, feature incompatibilities > are detected by comparing against the broker's own supported features. > * {{ApiVersionsResponse}} is now served containing supported and finalized > feature information (using the newly added tagged fields). -- This message was sent by Atlassian Jira (v8.3.4#803005)