[
https://issues.apache.org/jira/browse/KAFKA-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14103592#comment-14103592
]
Joe Stein commented on KAFKA-1485:
----------------------------------
There are a lot of bug fixes in 3.4.6
(http://zookeeper.apache.org/doc/r3.4.6/releasenotes.html ) specifically this
one that [~nehanarkhede] reported
https://issues.apache.org/jira/browse/ZOOKEEPER-1382. This may only affect the
server? If we release with 3.4.5 aren't we telling people that 3.4.5 that it is
ok to use? Is this bug or another going to be a Kafka problem? It seems wrong
to be releasing against a non stable apache project version if we don't have
too.
I think Gwen's patch for 3.4.6 looked fine though I would suggest maybe a
different name for the class and instead have a comment inside of the class
regarding the zk ticket number since we might have to look at it for a while.
> 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)
