You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@livy.apache.org by GitBox <gi...@apache.org> on 2019/11/22 13:36:40 UTC

[GitHub] [incubator-livy] symat opened a new pull request #262: [LIVY-717] introduce maven property to set ZooKeeper version

symat opened a new pull request #262: [LIVY-717] introduce maven property to set ZooKeeper version
URL: https://github.com/apache/incubator-livy/pull/262
 
 
   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.
   
   see https://issues.apache.org/jira/browse/LIVY-717
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services