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

Sakthi commented on HBASE-22172:
--------------------------------

Yes [~elserj] you are right. I am not sure if there is any way we can do this 
testing currently via Jenkins. Also I'm not sure if these are the complete of 
list of warnings that we might see. Some other type of invocations 
(pe,ltt,itbll, other mr jobs, etc) might list out other set of warnings. The 
above 250 were hit with hbase shell's mere invocation alone. So this is bad if 
we have to try all other possible ways as well to access[thrift, rest] (to list 
out all such warnings). 

> 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)

Reply via email to