[jira] [Updated] (LIVY-717) Specify explicit ZooKeeper version in maven

["Mate Szalay-Beko (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LIVY-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mate Szalay-Beko updated LIVY-717:
----------------------------------
    Description: 
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.


  was:
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)


> 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
>            Priority: Major
>          Time Spent: 10m
>  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)