You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "kaushik srinivas (Jira)" <ji...@apache.org> on 2022/01/07 07:23:00 UTC
[jira] [Created] (KAFKA-13578) Need clarity on the bridge release version of kafka without zookeeper in the eco system - KIP500
kaushik srinivas created KAFKA-13578:
----------------------------------------
Summary: Need clarity on the bridge release version of kafka without zookeeper in the eco system - KIP500
Key: KAFKA-13578
URL: https://issues.apache.org/jira/browse/KAFKA-13578
Project: Kafka
Issue Type: Bug
Reporter: kaushik srinivas
We see from the KIP-500
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-500%3A+Replace+ZooKeeper+with+a+Self-Managed+Metadata+Quorum]
Below statement needs some clarity,
*We will be able to upgrade from any version of Kafka to this bridge release, and from the bridge release to a post-ZK release. When upgrading from an earlier release to a post-ZK release, the upgrade must be done in two steps: first, you must upgrade to the bridge release, and then you must upgrade to the post-ZK release.*
What apache kafka version is referred to as bridge release in this context ? can apache kafka 3.0.0 be considered bridge release even though it is not production ready to run without zookeeper ?
--
This message was sent by Atlassian Jira
(v8.20.1#820001)