Re: Upgrade required Java version to 1.8 on 3.5+

Hi Shawn, Thanks for the feedback and thanks for everybody else too. The short term plan is to introduce Java 8 in next upcoming stable release, 3.5. Jumping 2 Java versions seems to be too much for me too. ZK master branch is going to be 3.6 release in which we can talk about upgrading to Java

Re: Upgrade required Java version to 1.8 on 3.5+

On 3/7/2018 1:21 PM, Jeff Widman wrote: > +1 from me to using Java 8 or even going all the way to 9 for the 3.5 > release branch. I don't think it would be a good idea to require Java 9 at this time.  It's probably already an uphill battle for sysadmins to get approval to jump ONE major version. 

Re: Upgrade required Java version to 1.8 on 3.5+

+1 from me to using Java 8 or even going all the way to 9 for the 3.5 release branch. On Mar 7, 2018 8:17 AM, "Shawn Heisey" wrote: > On 3/7/2018 4:04 AM, Andor Molnar wrote: > >> I've quickly checked some of the major components that are heavy Zk >> clients: >> >>

Re: Upgrade required Java version to 1.8 on 3.5+

On 3/7/2018 4:04 AM, Andor Molnar wrote: I've quickly checked some of the major components that are heavy Zk clients: Hadoop/HDFS = 1.8 required HBase = 1.8 required Kafka = 1.7 required (has some 1.8 and 1.9 bindings) Hive = 1.8 required Curator = 1.7 required (has 1.8-only async module to

Re: Upgrade required Java version to 1.8 on 3.5+

Hi, At BookKeeper we are supporting java 8 onwards and we are using 3.5 branch. (Speaking as BookKeeper PMC) In my company we running all on java8 and we switching to java9, both clients and servers So good to see Zookeeper moving to java8 Enrico Il mer 7 mar 2018, 12:04 Andor Molnar

Upgrade required Java version to 1.8 on 3.5+

Hi ZooKeeper users, There's an ongoing discussion on the dev list about upgrading the required Java version to 1.8 on trunk and 3.5 branches. We'd like to get some feedback from a bigger audience if anybody or any other component that is dependent on ZooKeeper has any concerns or objections