Re: Proposal: require Java7 for Cassandra 2.0
+1 - Aaron Morton Freelance Cassandra Developer New Zealand @aaronmorton http://www.thelastpickle.com On 7/02/2013, at 11:21 AM, Jonathan Ellis jbel...@gmail.com wrote: Java 6 EOL is this month. Java 7 will be two years old when C* 2.0 comes out (July). Anecdotally, a bunch of people are running C* on Java7 with no issues, except for the Snappy-on-OS-X problem (which will be moot if LZ4 becomes our default, as looks likely). Upgrading to Java7 lets us take advantage of new (two year old) features as well as simplifying interoperability with other dependencies, e.g., Jetty's BlockingArrayQueue requires java7. Thoughts? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Proposal: require Java7 for Cassandra 2.0
+1 Regards, /VJ On Wed, Feb 6, 2013 at 2:21 PM, Jonathan Ellis jbel...@gmail.com wrote: Java 6 EOL is this month. Java 7 will be two years old when C* 2.0 comes out (July). Anecdotally, a bunch of people are running C* on Java7 with no issues, except for the Snappy-on-OS-X problem (which will be moot if LZ4 becomes our default, as looks likely). Upgrading to Java7 lets us take advantage of new (two year old) features as well as simplifying interoperability with other dependencies, e.g., Jetty's BlockingArrayQueue requires java7. Thoughts? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Proposal: require Java7 for Cassandra 2.0
unsubscribe On Thu, Feb 7, 2013 at 12:58 PM, Ajith Kannan kann...@mail.montclair.eduwrote: +1 On 2/6/2013 9:13 PM, Jake Luciani wrote: +1 On Wed, Feb 6, 2013 at 5:32 PM, Gary Dusbabekgdusba...@gmail.com wrote: +1 On Wed, Feb 6, 2013 at 4:21 PM, Jonathan Ellisjbel...@gmail.com wrote: Java 6 EOL is this month. Java 7 will be two years old when C* 2.0 comes out (July). Anecdotally, a bunch of people are running C* on Java7 with no issues, except for the Snappy-on-OS-X problem (which will be moot if LZ4 becomes our default, as looks likely). Upgrading to Java7 lets us take advantage of new (two year old) features as well as simplifying interoperability with other dependencies, e.g., Jetty's BlockingArrayQueue requires java7. Thoughts? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Proposal: require Java7 for Cassandra 2.0
http://i.imgur.com/kQWV2.gif On Thu, Feb 7, 2013 at 9:38 PM, Anton Prakash anton.prak...@cloudtalk.com wrote: unsubscribe On Thu, Feb 7, 2013 at 12:58 PM, Ajith Kannan kann...@mail.montclair.eduwrote: +1 On 2/6/2013 9:13 PM, Jake Luciani wrote: +1 On Wed, Feb 6, 2013 at 5:32 PM, Gary Dusbabekgdusba...@gmail.com wrote: +1 On Wed, Feb 6, 2013 at 4:21 PM, Jonathan Ellisjbel...@gmail.com wrote: Java 6 EOL is this month. Java 7 will be two years old when C* 2.0 comes out (July). Anecdotally, a bunch of people are running C* on Java7 with no issues, except for the Snappy-on-OS-X problem (which will be moot if LZ4 becomes our default, as looks likely). Upgrading to Java7 lets us take advantage of new (two year old) features as well as simplifying interoperability with other dependencies, e.g., Jetty's BlockingArrayQueue requires java7. Thoughts? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- Eric Evans Acunu | http://www.acunu.com | @acunu
Re: Proposal: require Java7 for Cassandra 2.0
Counter proposal java 8 and closures. Jk On Thursday, February 7, 2013, Carl Yeksigian c...@yeksigian.com wrote: +1 On Wed, Feb 6, 2013 at 5:21 PM, Jonathan Ellis jbel...@gmail.com wrote: Java 6 EOL is this month. Java 7 will be two years old when C* 2.0 comes out (July). Anecdotally, a bunch of people are running C* on Java7 with no issues, except for the Snappy-on-OS-X problem (which will be moot if LZ4 becomes our default, as looks likely). Upgrading to Java7 lets us take advantage of new (two year old) features as well as simplifying interoperability with other dependencies, e.g., Jetty's BlockingArrayQueue requires java7. Thoughts? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Proposal: require Java7 for Cassandra 2.0
+1 -- Pavel Yaskevich On Wednesday, February 6, 2013 at 2:21 PM, Jonathan Ellis wrote: Java 6 EOL is this month. Java 7 will be two years old when C* 2.0 comes out (July). Anecdotally, a bunch of people are running C* on Java7 with no issues, except for the Snappy-on-OS-X problem (which will be moot if LZ4 becomes our default, as looks likely). Upgrading to Java7 lets us take advantage of new (two year old) features as well as simplifying interoperability with other dependencies, e.g., Jetty's BlockingArrayQueue requires java7. Thoughts? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Proposal: require Java7 for Cassandra 2.0
+1 -- AY On Thursday, February 7, 2013 at 01:24 AM, Pavel Yaskevich wrote: +1 -- Pavel Yaskevich On Wednesday, February 6, 2013 at 2:21 PM, Jonathan Ellis wrote: Java 6 EOL is this month. Java 7 will be two years old when C* 2.0 comes out (July). Anecdotally, a bunch of people are running C* on Java7 with no issues, except for the Snappy-on-OS-X problem (which will be moot if LZ4 becomes our default, as looks likely). Upgrading to Java7 lets us take advantage of new (two year old) features as well as simplifying interoperability with other dependencies, e.g., Jetty's BlockingArrayQueue requires java7. Thoughts? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Proposal: require Java7 for Cassandra 2.0
There seems to be a lot of confusion on this topic in the C* Community. Most people look at the Datastax docs that recommend Java 6 and ask why that recommendation is there. Threads never seem to finish with a clear definitive answer. There seem to be about 3-4 of these for the past few months on the Users list. I love the idea of requiring Java 7 explicitly + clarifying the project's stance on the JVM requirement overall. Might also want to lock it down to something like Java 7 u8 (u13 might be even nicer given 2.0's timeframe) given the early instability in Java7's early releases (and I guess allow but maybe warn for OpenJDK7?). My 2-cents. Best, Michael On 2/6/13 2:21 PM, Jonathan Ellis jbel...@gmail.com wrote: Java 6 EOL is this month. Java 7 will be two years old when C* 2.0 comes out (July). Anecdotally, a bunch of people are running C* on Java7 with no issues, except for the Snappy-on-OS-X problem (which will be moot if LZ4 becomes our default, as looks likely). Upgrading to Java7 lets us take advantage of new (two year old) features as well as simplifying interoperability with other dependencies, e.g., Jetty's BlockingArrayQueue requires java7. Thoughts? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Proposal: require Java7 for Cassandra 2.0
On Wed, Feb 6, 2013 at 4:21 PM, Jonathan Ellis jbel...@gmail.com wrote: Java 6 EOL is this month. Java 7 will be two years old when C* 2.0 comes out (July). Anecdotally, a bunch of people are running C* on Java7 with no issues, except for the Snappy-on-OS-X problem (which will be moot if LZ4 becomes our default, as looks likely). Upgrading to Java7 lets us take advantage of new (two year old) features as well as simplifying interoperability with other dependencies, e.g., Jetty's BlockingArrayQueue requires java7. Thoughts? We already do quite a bit of jdk version/type detection in cassandra-env.sh so we can catch it early if they try to use java6 and give a meaningful error, so this sounds good to me. -Brandon
Re: Proposal: require Java7 for Cassandra 2.0
+1 On Wed, Feb 6, 2013 at 2:29 PM, Brandon Williams dri...@gmail.com wrote: On Wed, Feb 6, 2013 at 4:21 PM, Jonathan Ellis jbel...@gmail.com wrote: Java 6 EOL is this month. Java 7 will be two years old when C* 2.0 comes out (July). Anecdotally, a bunch of people are running C* on Java7 with no issues, except for the Snappy-on-OS-X problem (which will be moot if LZ4 becomes our default, as looks likely). Upgrading to Java7 lets us take advantage of new (two year old) features as well as simplifying interoperability with other dependencies, e.g., Jetty's BlockingArrayQueue requires java7. Thoughts? We already do quite a bit of jdk version/type detection in cassandra-env.sh so we can catch it early if they try to use java6 and give a meaningful error, so this sounds good to me. -Brandon
Re: Proposal: require Java7 for Cassandra 2.0
+1 On Wed, Feb 6, 2013 at 4:21 PM, Jonathan Ellis jbel...@gmail.com wrote: Java 6 EOL is this month. Java 7 will be two years old when C* 2.0 comes out (July). Anecdotally, a bunch of people are running C* on Java7 with no issues, except for the Snappy-on-OS-X problem (which will be moot if LZ4 becomes our default, as looks likely). Upgrading to Java7 lets us take advantage of new (two year old) features as well as simplifying interoperability with other dependencies, e.g., Jetty's BlockingArrayQueue requires java7. Thoughts? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
Re: Proposal: require Java7 for Cassandra 2.0
+1 On Wed, Feb 6, 2013 at 5:32 PM, Gary Dusbabek gdusba...@gmail.com wrote: +1 On Wed, Feb 6, 2013 at 4:21 PM, Jonathan Ellis jbel...@gmail.com wrote: Java 6 EOL is this month. Java 7 will be two years old when C* 2.0 comes out (July). Anecdotally, a bunch of people are running C* on Java7 with no issues, except for the Snappy-on-OS-X problem (which will be moot if LZ4 becomes our default, as looks likely). Upgrading to Java7 lets us take advantage of new (two year old) features as well as simplifying interoperability with other dependencies, e.g., Jetty's BlockingArrayQueue requires java7. Thoughts? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced -- http://twitter.com/tjake
Re: Proposal: require Java7 for Cassandra 2.0
+1 -- Sylvain On Wed, Feb 6, 2013 at 11:21 PM, Jonathan Ellis jbel...@gmail.com wrote: Java 6 EOL is this month. Java 7 will be two years old when C* 2.0 comes out (July). Anecdotally, a bunch of people are running C* on Java7 with no issues, except for the Snappy-on-OS-X problem (which will be moot if LZ4 becomes our default, as looks likely). Upgrading to Java7 lets us take advantage of new (two year old) features as well as simplifying interoperability with other dependencies, e.g., Jetty's BlockingArrayQueue requires java7. Thoughts? -- Jonathan Ellis Project Chair, Apache Cassandra co-founder, http://www.datastax.com @spyced
