cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8168) Require Java 8
Date Mon, 24 Nov 2014 10:19:12 GMT


Sylvain Lebresne commented on CASSANDRA-8168:

bq.  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.

For what it's worth, I'm mildly a fan of this. It's a bit unclear to me that getting java
8 in 3.0 is such a big deal, but buying one more year of painful merge is a big deal. Getting
nashorn is nice, but for UDF I think we'll end up with mostly recommending people to use JAVA
directly and so I don't think it's a huge deal. As for CASSANDRA-5239, how sure are we that
we'll have this done in 3.0? And that {{CompletableFuture}} gives us something that guava's
{{ListenableFuture}} don't give us?

> 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