[
https://issues.apache.org/jira/browse/LIVY-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Saisai Shao resolved LIVY-717.
------------------------------
Fix Version/s: 0.7.0
Assignee: Mate Szalay-Beko
Resolution: Fixed
Issue resolved by pull request 262
https://github.com/apache/incubator-livy/pull/262
> 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
> Assignee: Mate Szalay-Beko
> Priority: Major
> Fix For: 0.7.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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]. Now I
> want to test Livy in a cluster where we have a new ZooKeeper 3.5 deployed.
> When we want to use Livy in a cluster where a newer ZooKeeper server version
> is used, we might run into run-time errors if we compile Livy using the
> current Curator / Hadoop versions. The Curator version can already explicitly
> set with the {{curator.version}} maven property in build time, but we were
> still missed the same parameter for ZooKeeper.
> In this PR I added a new maven parameter called {{zookeeper.version}} and
> after analyzing the maven dependency tree, I made sure that the Curator and
> ZooKeeper versions used in compile time are always harmonized and controlled
> by the maven parameters.
> I set the zookeeper.version in maven to {{3.4.6}} to be backward compatible
> with the current Livy dependencies.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
