[jira] [Resolved] (HBASE-26773) [hbase-thirdparty] Introduce a hbase-unsafe module in hbase-thirdparty to remove the direct references of Unsafe in our main code base

["Duo Zhang (Jira)" <ji...@apache.org>]

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

Duo Zhang resolved HBASE-26773.
-------------------------------
    Fix Version/s: thirdparty-4.1.0
     Hadoop Flags: Reviewed
     Release Note: Introduced a new hbase-unsafe module in hbase-thirdparty.
       Resolution: Fixed

> [hbase-thirdparty] Introduce a hbase-unsafe module in hbase-thirdparty to remove the direct references of Unsafe in our main code base
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-26773
>                 URL: https://issues.apache.org/jira/browse/HBASE-26773
>             Project: HBase
>          Issue Type: Improvement
>          Components: compatibility, thirdparty
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: thirdparty-4.1.0
>
>
> For java 9+, sun.misc.Unsafe is in the module jdk.unsupported. When compiling with java 11 --release 8, these symbols will not be exported and lead to compile errors.
> There is a jdk issue
> https://bugs.openjdk.java.net/browse/JDK-8214165
> But seems the jdk team does not want to fix it. So if we want to move up to java 11 but still keep the java 8 compatibility, a possible choice is to remove the direct reference of sun.misc.Unsafe so at compile time there will be no problem, and at runtime we export the jdk.unsupported so there will be no problem too.
> For more details, please see the discussion of this thread on the dev mailing list.
> https://lists.apache.org/thread/w5lrxkhswlonj09xf9hcwgvck3nsjdfx



--
This message was sent by Atlassian Jira
(v8.20.1#820001)