[
https://issues.apache.org/jira/browse/FLINK-34415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Visser updated FLINK-34415:
-----------------------------------
Description:
The current Flink Kafka connector still uses Zookeeper for Kafka-based testing.
Since Kafka 3.3, KRaft has been marked as production ready [1]. In order to
reduce tech debt, we should remove all the dependencies on Zookeeper and only
uses KRaft for the Flink Kafka connector.
[1]
https://cwiki.apache.org/confluence/display/KAFKA/KIP-833%3A+Mark+KRaft+as+Production+Ready
was:
The current Flink Kafka connector still uses Zookeeper for Kafka-based testing.
Since Kafka 3.4, KRaft has been marked as production ready [1]. In order to
reduce tech debt, we should remove all the dependencies on Zookeeper and only
uses KRaft for the Flink Kafka connector.
[1]
https://cwiki.apache.org/confluence/display/KAFKA/KIP-833%3A+Mark+KRaft+as+Production+Ready
> Move away from Kafka-Zookeeper based tests in favor of Kafka-KRaft
> ------------------------------------------------------------------
>
> Key: FLINK-34415
> URL: https://issues.apache.org/jira/browse/FLINK-34415
> Project: Flink
> Issue Type: Technical Debt
> Components: Connectors / Kafka
> Reporter: Martijn Visser
> Priority: Major
>
> The current Flink Kafka connector still uses Zookeeper for Kafka-based
> testing. Since Kafka 3.3, KRaft has been marked as production ready [1]. In
> order to reduce tech debt, we should remove all the dependencies on Zookeeper
> and only uses KRaft for the Flink Kafka connector.
> [1]
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-833%3A+Mark+KRaft+as+Production+Ready
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
