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

Ankit Singhal commented on HBASE-20172:
---------------------------------------

bq. is there a reason to do this in java8?
I believe setting current classloader to null and relying on Java to fallback 
to system classloader is not a good idea as every Java API would not be 
handling this consistently.

> During coprocessor load, switch classloader only if it's a custom CP.
> ---------------------------------------------------------------------
>
>                 Key: HBASE-20172
>                 URL: https://issues.apache.org/jira/browse/HBASE-20172
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Ankit Singhal
>            Assignee: Ankit Singhal
>            Priority: Major
>             Fix For: 2.0.0
>
>         Attachments: HBASE-20172.patch
>
>
> Current Impact:- 
> Metric registries will not be able to load its implementation through service 
> loader and etc.
> We are not observing this with Java8 because ServiceLoader uses system class 
> loader if provided class loader is null but it gets exposed with Java7 
> easily(TEPHRA-285)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to