cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Stupp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-11987) Cassandra support for JDK 9
Date Fri, 10 Jun 2016 12:36:21 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-11987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Stupp resolved CASSANDRA-11987.
--------------------------------------
    Resolution: Duplicate

This issue is already mentioned in CASSANDRA-9608. At the moment, Java 9 is not production
ready and changes a lot of things. Since it's still 8 or 9 (?) months until Java 9 release,
it's not really critical. Let's see, how it looks then in a few months.

> Cassandra support for JDK 9
> ---------------------------
>
>                 Key: CASSANDRA-11987
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11987
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>         Environment: JDK9
>            Reporter: shylaja kokoori
>            Priority: Minor
>
> Hi,
> I tried to compile Cassandra with JDK 9 and ran into compilation issues because monitorEnter/monitorExit
functions have been removed from sun.misc.Unsafe in JDK9 (http://mail.openjdk.java.net/pipermail/jdk9-hs-rt-changes/2015-January/000773.html).
> Is there a specific reason why Cassandra uses these Unsafe APIs instead of say java.util.concurrent.locks?
> Thanks,
> shylaja



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message