We've reverted all machines back to Java 6 after running into numerous Java 7 issues...some running Cassandra, some running Zookeeper, others just general problems.  I don't recall any other major language release being such a mess.


On Fri, Dec 14, 2012 at 5:07 PM, Bill de hÓra <bill@dehora.net> wrote:
"At least that would be one way of defining "officially supported".

Not quite, because, Datastax is not Apache Cassandra.

"the only issue related to Java 7 that I know of is CASSANDRA-4958, but that's osx specific (I wouldn't advise using osx in production anyway) and it's not directly related to Cassandra anyway so you can easily use the beta version of snappy-java as a workaround if you want to. So that non blocking issue aside, and as far as we know, Cassandra supports Java 7. Is it rock-solid in production? Well, only repeated use in production can tell, and that's not really in the hand of the project."

Exactly right. If enough people use Cassandra on Java7 and enough people file bugs about Java 7 and enough people work on bugs for Java 7 then Cassandra will eventually work well enough on Java7.

Bill

On 14 Dec 2012, at 19:43, Drew Kutcharian <drew@venarc.com> wrote:

> In addition, the DataStax official documentation states: "Versions earlier than 1.6.0_19 should not be used. Java 7 is not recommended."
>
> http://www.datastax.com/docs/1.1/install/install_rpm
>
>
>
> On Dec 14, 2012, at 9:42 AM, Aaron Turner <synfinatic@gmail.com> wrote:
>
>> Does Datastax (or any other company) support Cassandra under Java 7?
>> Or will they tell you to downgrade when you have some problem, because
>> they don't support C* running on 7?
>>
>> At least that would be one way of defining "officially supported".
>>
>> On Fri, Dec 14, 2012 at 2:22 AM, Sylvain Lebresne <sylvain@datastax.com> wrote:
>>> What kind of official statement do you want? As far as I can be considered
>>> an official voice of the project, my statement is: "various people run in
>>> production with Java 7 and it seems to work".
>>>
>>> Or to answer the initial question, the only issue related to Java 7 that I
>>> know of is CASSANDRA-4958, but that's osx specific (I wouldn't advise using
>>> osx in production anyway) and it's not directly related to Cassandra anyway
>>> so you can easily use the beta version of snappy-java as a workaround if you
>>> want to. So that non blocking issue aside, and as far as we know, Cassandra
>>> supports Java 7. Is it rock-solid in production? Well, only repeated use in
>>> production can tell, and that's not really in the hand of the project. We do
>>> obviously encourage people to try Java 7 as much as possible and report any
>>> problem they may run into, but I would have though this goes without saying.
>>>
>>>
>>> On Fri, Dec 14, 2012 at 4:05 AM, Rob Coli <rcoli@palominodb.com> wrote:
>>>>
>>>> On Thu, Dec 13, 2012 at 11:43 AM, Drew Kutcharian <drew@venarc.com> wrote:
>>>>> With Java 6 begin EOL-ed soon
>>>>> (https://blogs.oracle.com/java/entry/end_of_public_updates_for), what's the
>>>>> status of Cassandra's Java 7 support? Anyone using it in production? Any
>>>>> outstanding *known* issues?
>>>>
>>>> I'd love to see an official statement from the project, due to the
>>>> sort of EOL issues you're referring to. Unfortunately previous
>>>> requests on this list for such a statement have gone unanswered.
>>>>
>>>> The non-official response is that various people run in production
>>>> with Java 7 and it seems to work. :)
>>>>
>>>> =Rob
>>>>
>>>> --
>>>> =Robert Coli
>>>> AIM&GTALK - rcoli@palominodb.com
>>>> YAHOO - rcoli.palominob
>>>> SKYPE - rcoli_palominodb
>>>
>>>
>>
>>
>>
>> --
>> Aaron Turner
>> http://synfin.net/         Twitter: @synfinatic
>> http://tcpreplay.synfin.net/ - Pcap editing and replay tools for Unix & Windows
>> Those who would give up essential Liberty, to purchase a little temporary
>> Safety, deserve neither Liberty nor Safety.
>>   -- Benjamin Franklin
>> "carpe diem quam minimum credula postero"
>