Date: Tue, 19 Mar 2024 01:38:38 +0000 (UTC) Message-ID: <1196067873.52646.1710812318301@cwiki-he-fi.apache.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_52645_1047840847.1710812318301" ------=_Part_52645_1047840847.1710812318301 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Current state: Accepted
Discussion thread: here
JIRA: KAFKA-4060
Released: 0.10.2.0
Please keep the discussion on the mailing list rather than commenting on= the wiki (wiki discussions get unwieldy fast).
This KIP r= emoves the Zookeeper dependency from Kafka Streams. Currently, for Kafka St= reams API accesses Zookeeper directly to create internal topics. We will us= e the client admin API introduced in KIP-4 to manage the internal topics vi= a Kafka broker instead of directly accessing Zookeeper.
Zookeeper related config value, ZOOKEEPER_CONNECT_CONFIG in StreamsConfi= g, is deprecated.
We add a n= ew KafkaStreams client which is used for internal topic management in Kafka= Streams API. We will remove the dependency to Zookeeper from Kafka Streams= API..
This feature is backward compatible from API perspective and no changes = need to be done to streaming apps. However, if kafka cluster is secured the= cluster admin should grant required privileges to the streaming app as des= cribed below.
Zookeeper related config value, ZOOKEEPER_CONNECT_CONFIG in= StreamsConfig, is deprecated.
In the current version of Kafka Streams user app needs to have proper ac= cess privileges to the zookeeper in order to manage internal topics. After = the changes proposed in this KIP user app will not need such privileges, ho= wever, user app will need new privileges in order to use Client Admin to ma= nage the internal topics. Streaming application should have the following p= rivileges for Client Admin:
User information need to be set the same way it is set in the streaming = app if the cluster is secured.
The same tests that are currently used will be used for testing the = new internal topic creation.
N/A.= em>