[
https://issues.apache.org/jira/browse/HBASE-25251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17227349#comment-17227349
]
Anoop Sam John commented on HBASE-25251:
----------------------------------------
Can we consider tightening our Unsafe avail checker to check whether all the
required methods are really available also? It would be good if our logic can
check whether to use Unsafe or not rather than asking customer to config it.
Thoughts?
> Enable configuration based enable/disable of Unsafe package usage
> -----------------------------------------------------------------
>
> Key: HBASE-25251
> URL: https://issues.apache.org/jira/browse/HBASE-25251
> Project: HBase
> Issue Type: Improvement
> Reporter: Sandeep Guggilam
> Assignee: Sandeep Guggilam
> Priority: Major
>
> We need a provide away for clients to disable Unsafe package usage .
> Currently there is no way for clients to specify that they don't want to use
> Unsafe conversion for Bytes conversion.
> As a result there could be some issues with missing methods of Unsafe when
> client is on JDK 11 . So the clients can disable Unsafe package use and use
> normal conversion if they want to.
> Also we use static references to Unsafe Availability in Bytes class assuming
> that the Unsafe availability is set during class loading and no one can ever
> override it later. Now that we plan to expose a util for clients to override
> the availability if required, we need to avoid the static references for
> computing the availability whenever we do the comparisions
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
