cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8168) Require Java 8
Date Sun, 23 Nov 2014 14:19:14 GMT


Aleksey Yeschenko commented on CASSANDRA-8168:

Fair enough.

I believe the right way to handle this switch (and the next one, to Java 9, whenever that
happens) is to extend the support period for the pre-switch Cassandra version. In other words,
extend Cassandra 2.1 EOL by at least one year longer than we usually do. People stuck with
Java 7 won't be able to go to C* 3.0 (until they get unstuck), but won't have to deal with
an abandoned Cassandra version, either.

It's been a month now since the ticket creation, and there hasn't been substantial opposition
to the idea, despite all the calls to people to voice their concerns. Given the new speed
that Java versions seem to be released at now (and EOL'd, too), and all the nice things in
Java 8, I suggest we make the formal decision to switch to Java 8 for Cassandra 3.0, now,
and start using it immediately after that.

> Require Java 8
> --------------
>                 Key: CASSANDRA-8168
>                 URL:
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: T Jake Luciani
>            Assignee: T Jake Luciani
>             Fix For: 3.0
> This is to discuss requiring Java 8 for version >= 3.0  
> There are a couple big reasons for this.
> * Better support for complex async work  e.g (CASSANDRA-5239)
> * Use Nashorn for Javascript UDFs CASSANDRA-7395

This message was sent by Atlassian JIRA

View raw message