[ 
https://issues.apache.org/jira/browse/HBASE-22172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028281#comment-17028281
 ] 

Duo Zhang commented on HBASE-22172:
-----------------------------------

[~ndimiduk] Ideally we should change to use new APIs but actually we can not, 
as we have lots of dependency which rely on the old internal APIs, for example, 
netty. So I think we'd better add these flags for now, and start to replace the 
old APIs with new APIs.

But I do not think it is easy. Java11 and Java8 are two different worlds. Maybe 
we have to change the whole architecture of HBase if we want to fully support 
Java11's modular system, which may take another decade...

> Suppress Java 11 reflective access warnings
> -------------------------------------------
>
>                 Key: HBASE-22172
>                 URL: https://issues.apache.org/jira/browse/HBASE-22172
>             Project: HBase
>          Issue Type: Sub-task
>          Components: java, scripts
>            Reporter: Sakthi
>            Assignee: Sakthi
>            Priority: Minor
>              Labels: jdk11
>         Attachments: hbase-22172.master.001.patch
>
>
> While running a Java 8 compiled hbase on Java 11 system, I found the 
> following warnings being thrown. I think we can add the "--add-opens" flag to 
> HBASE_OPTS (if the jdk version is 11) to suppress this warning.
> {code:java}
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> org.apache.hadoop.hbase.util.UnsafeAvailChecker 
> (file:/Users/jatsakthi/test/HBASE_TEST_AREA/hbase-3.0.0-SNAPSHOT/lib/hbase-common-3.0.0-SNAPSHOT.jar)
>  to method java.nio.Bits.unaligned()
> WARNING: Please consider reporting this to the maintainers of 
> org.apache.hadoop.hbase.util.UnsafeAvailChecker
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to