[
https://issues.apache.org/jira/browse/HBASE-22172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814564#comment-16814564
]
Josh Elser commented on HBASE-22172:
------------------------------------
bq. I tried hbase shell using --illegal-access=warn to list out all the
warnings. It listed around 250 warnings
You used the output from illegal-access to generate the list of warnings, to
then figure out the open-adds that you needed to use?
Best as I can find with some quick searching, it doesn't like the the JDK devs
gave us a convenient solution. At least this one (reasonable to me) ask went
silent
http://mail.openjdk.java.net/pipermail/jigsaw-dev/2017-January/010749.html
I guess there's no good way for us to automate what you're testing locally via
Jenkins, is there?
> Suppress Java 11 reflective access warnings
> -------------------------------------------
>
> Key: HBASE-22172
> URL: https://issues.apache.org/jira/browse/HBASE-22172
> Project: HBase
> Issue Type: Task
> Reporter: Sakthi
> Assignee: Sakthi
> Priority: Major
> 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
(v7.6.3#76005)
