[
https://issues.apache.org/jira/browse/KAFKA-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107090#comment-14107090
]
Joe Stein commented on KAFKA-1485:
----------------------------------
>From the community perspective I don't want us to have to tell someone that
>uses and launches zookeeper 3.4.5 from our release that hits a known defect
>that they have to upgrade. There are Kafka users that don't use zookeeper for
>any thing else but Kafka and launch it from the release.
There have been a few cases where kafka code is introduced to work around
dependency issues I just think it is a bad precident to expose that in the
class name.
Could you please change the class name and then we can move ahead with 3.4.6?
> Upgrade to Zookeeper 3.4.6 and create "shim" for ZKCLI so system tests can run
> ------------------------------------------------------------------------------
>
> Key: KAFKA-1485
> URL: https://issues.apache.org/jira/browse/KAFKA-1485
> Project: Kafka
> Issue Type: Wish
> Affects Versions: 0.8.1.1
> Reporter: Machiel Groeneveld
> Assignee: Gwen Shapira
> Labels: newbie
> Fix For: 0.8.2
>
> Attachments: KAFKA-1485.2.patch, KAFKA-1485.3.patch, KAFKA-1485.patch
>
>
> I can't run projects alongside Kafka that use zookeeper 3.4 jars. 3.4 has
> been out for 2.5 years and seems to be ready for adoption.
> In particular Apache Storm will upgrade to Zookeeper 3.4.x in their next
> 0.9.2 release. I can't run both versions in my tests at the same time.
> The only compile problem I saw was in EmbeddedZookeeper.scala
--
This message was sent by Atlassian JIRA
(v6.2#6252)
