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

ASF GitHub Bot commented on NIFI-2828:
--------------------------------------

GitHub user mattyb149 opened a pull request:

    https://github.com/apache/nifi/pull/1146

    NIFI-2828: Fixed issue with transitive Hadoop dependencies in Hive NAR

    
    


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

    $ git pull https://github.com/mattyb149/nifi NIFI-2828_2

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

    https://github.com/apache/nifi/pull/1146.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 #1146
    
----
commit 7b987df3b092280401cfc1115aa82a0b668a24cb
Author: Matt Burgess <mattyb...@apache.org>
Date:   2016-10-18T20:22:15Z

    NIFI-2828: Fixed issue with transitive Hadoop dependencies in Hive NAR

----


> SelectHiveQL and PutHiveQL fail with NoClassDefFoundError when using HTTP 
> transport 
> ------------------------------------------------------------------------------------
>
>                 Key: NIFI-2828
>                 URL: https://issues.apache.org/jira/browse/NIFI-2828
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Joey Frazee
>            Assignee: Matt Burgess
>             Fix For: 1.1.0
>
>
> SelectHiveQL and PutHiveQL don't currently work with HTTP transport. There 
> appears to be a class loader problem resulting in 
> java.lang.NoClassDefFoundError: Could not initialize class 
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.
> This looks like a conflict with the Apache commons httpclient version in 
> hadoop-common. Removing the hadoop-libraries .nar dependency and provided 
> scope for hadoop-common appears to fix the issue, but I haven't done any 
> rigorous testing so I'm not sure if there are other consequences or not.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to