Mate Szalay-Beko created LIVY-717:
-------------------------------------
Summary: Specify explicit ZooKeeper version in maven
Key: LIVY-717
URL: https://issues.apache.org/jira/browse/LIVY-717
Project: Livy
Issue Type: Improvement
Reporter: Mate Szalay-Beko
I want to test Livy in a cluster where we have a new ZooKeeper 3.5 deployed.
Currently in Livy we use Curator 2.7.1, which only supports ZooKeeper 3.4. I
want to use Curator 4.0.2, as it supports ZooKeeper 3.5. (Also Hadoop trunk was
updated recently to use Curator 4.0.2 and ZooKeeper 3.5.6, see
[HADOOP-16579|https://issues.apache.org/jira/browse/HADOOP-16579].)
When I tried to build Livy with Curator 4.0.2, I found out that Curator 4.x
brings a specific 3.5 beta ZooKeeper version as compile time dependency, which
is different from the stable 3.5.6 ZooKeeper version used in Hadoop. Also The
Hadoop version used in Livy brings different ZooKeeper version.
In this patch I don't I want to change the Curator or ZooKeeper versions, but I
want to enable the users to specify an explicit ZooKeeper version for Livy by a
maven parameter.
(the Curator version is already added as maven parameter)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
