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

ASF GitHub Bot commented on CAMEL-11692:
----------------------------------------

GitHub user jamesnetherton opened a pull request:

    https://github.com/apache/camel/pull/1899

    CAMEL-11692: Set ClassLoader property on HBase configuration

    https://issues.apache.org/jira/browse/CAMEL-11692

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jamesnetherton/camel CAMEL-11692

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1899.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1899
    
----
commit bcbf3e2009fc3b09d240b096c07001ddbd645e97
Author: James Netherton <[email protected]>
Date:   2017-08-23T08:11:39Z

    CAMEL-11692: Set ClassLoader property on HBase configuration

----


> Set ClassLoader property on HBase configuration
> -----------------------------------------------
>
>                 Key: CAMEL-11692
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11692
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-hbase
>    Affects Versions: 2.20.0
>            Reporter: James Netherton
>            Assignee: James Netherton
>            Priority: Minor
>
> Depending on the class loading environment, the way in which HBase attempts 
> to load configuration files from the classpath may silently fail.
> We should set the relevant ClassLoader on the HBase configuration instance so 
> we can load config resources correctly. 
> We can use the ApplicationContextClassLoader if it's available, else we just 
> fall back on whatever default ClassLoader HBase decides to use.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to