Hi All,

Presently BK is using ZK-3.4.3 version which I feel is quite old one. While 
bumping the version to ZK-3.4.6, I've noticed one small diff about the netty 
versions.

ZK has netty version - 3.7.0
BK has netty version - 3.2.9

As part of ZOOKEEPER-1715, it has upgraded the netty version to 3.7.0
<dependency org="io.netty" name="netty" conf="default" rev="3.7.0.Final">

But in BK we have different version 3.2.9
    <dependency>
      <groupId>org.jboss.netty</groupId>
      <artifactId>netty</artifactId>
      <version>3.2.9.Final</version>
      <scope>compile</scope>
    </dependency>


Following are few ideas that comes in my mind, which I'm putting to kick start 
the discussion.

Approach-1) Since BK is not using ZooKeeper's netty feature, it can simply 
exclude the netty library while adding ZK-3.4.6 dependency and BK will continue 
using his own version.
Approach-2) BK also will upgrade its netty version to '3.7.0' and be in sync 
with ZK-3.4.6. Here it would need to see old - new BK communications.

Appreciate any help in finding a better way. Also welcome fresh ideas:)

Thanks & Regards,
Rakesh R

Reply via email to