You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Manikumar (JIRA)" <ji...@apache.org> on 2017/08/19 16:15:01 UTC

[jira] [Resolved] (KAFKA-2053) Make initZk a protected function

     [ https://issues.apache.org/jira/browse/KAFKA-2053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manikumar resolved KAFKA-2053.
------------------------------
    Resolution: Won't Fix

 Pl reopen if you think the requirement still exists

> Make initZk a protected function
> --------------------------------
>
>                 Key: KAFKA-2053
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2053
>             Project: Kafka
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.8.2.0
>            Reporter: Christian Kampka
>            Priority: Minor
>         Attachments: make-initzk-protected
>
>
> In our environment, we have established an external procedure to notify clients of changes in the zookeeper cluster configuration, especially appearance and disappearance of nodes. it has also become quite common to run Kafka as an embedded service (especially in tests).
> When doing so, it would makes things easier if it were possible to manipulate the creation of the zookeeper client to supply Kafka with a specialized ZooKeeper client that is adjusted to our needs but of course API compatible with the ZkClient.
> Therefore, I would like to propose to make the initZk method protected so we will be able to simply override it for client creation. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)