Re: Proposal: require Java7 for Cassandra 2.0

2013-02-06 Thread Sylvain Lebresne
+1 -- Sylvain On Wed, Feb 6, 2013 at 11: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 i

Re: Proposal: require Java7 for Cassandra 2.0

2013-02-06 Thread Jake Luciani
+1 On Wed, Feb 6, 2013 at 5:32 PM, Gary Dusbabek wrote: > +1 > > > On Wed, Feb 6, 2013 at 4: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, ex

Re: Proposal: require Java7 for Cassandra 2.0

2013-02-06 Thread Gary Dusbabek
+1 On Wed, Feb 6, 2013 at 4: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

Re: Proposal: require Java7 for Cassandra 2.0

2013-02-06 Thread Jason Brown
+1 On Wed, Feb 6, 2013 at 2:29 PM, Brandon Williams wrote: > On Wed, Feb 6, 2013 at 4: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 fo

Re: Proposal: require Java7 for Cassandra 2.0

2013-02-06 Thread Brandon Williams
On Wed, Feb 6, 2013 at 4: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 d

Re: Proposal: require Java7 for Cassandra 2.0

2013-02-06 Thread Michael Kjellman
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

Re: Proposal: require Java7 for Cassandra 2.0

2013-02-06 Thread Tupshin Harper
+1 On Feb 6, 2013 5:22 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 def

Re: Proposal: require Java7 for Cassandra 2.0

2013-02-06 Thread Aleksey Yeschenko
+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 bu

Re: Proposal: require Java7 for Cassandra 2.0

2013-02-06 Thread Pavel Yaskevich
+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