[
https://issues.apache.org/jira/browse/HBASE-12108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14150283#comment-14150283
]
Aniket Bhatnagar commented on HBASE-12108:
------------------------------------------
Yes @stack, that's exactly the reason. My proposal is to call
conf.setClassLoader(this.getClass().getClassLoader()) before calling
addHbaseResources in the static create method.
A workaround to this is that the user should set context classloader (using
Thread.currentThread().setClassLoader()) before calling
HBaseConfiguration.create().
> HBaseConfiguration
> ------------------
>
> Key: HBASE-12108
> URL: https://issues.apache.org/jira/browse/HBASE-12108
> Project: HBase
> Issue Type: Bug
> Components: Client
> Reporter: Aniket Bhatnagar
> Priority: Minor
>
> IN the setup wherein HBase jars are loaded in child classloader whose parent
> had loaded hadoop-common jar, HBaseConfiguration.create() throws
> "hbase-default.xml file seems to be for and old version of HBase (null)... "
> exception. ClassLoader should be set in Hadoop conf object before calling
> addHbaseResources method
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
