[
https://issues.apache.org/jira/browse/KAFKA-16868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-16868:
------------------------------------
Component/s: streams
> Post KIP-924 StreamsPartitionAssignor code cleanup
> --------------------------------------------------
>
> Key: KAFKA-16868
> URL: https://issues.apache.org/jira/browse/KAFKA-16868
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: A. Sophie Blee-Goldman
> Priority: Major
>
> Making an umbrella task for all of the tech debt and code consolidation
> cleanup work that can/should be done following the implementation of
> [KIP-924: customizable task assignment for
> Streams|https://cwiki.apache.org/confluence/display/KAFKA/KIP-924%3A+customizable+task+assignment+for+Streams]
> Most of this revolves around deduplicating code once it's no longer needed,
> including classes like the ClientState, StandbyTaskAssignor and related
> elements, and the old TaskAssignor interface along with its implementations.
> Note that in 3.8, the first version in which KIP-924 was released, we just
> added the new public config and new TaskAssignor interface but did not get
> rid of the old internal config or old TaskAssignor interface. If neither
> config is set in 3.8 we still default to the old HAAssignor, as a kind of
> opt-in feature flag, and internally will convert the output of the new
> TaskAssignor into the old style of ClientState-based assignment tracking. We
> intend to clean up all of the old code and eventually support only the new
> TaskAssignor interface as well as converting everything internally from the
> ClientState to the TaskAssignment/KafkaStreamsAssignment style output
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
