You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Bryan Rosander (JIRA)" <ji...@apache.org> on 2017/03/01 17:25:45 UTC

[jira] [Updated] (NIFI-3530) PutHiveStreaming doesn't fully utilize *-site.xml files

     [ https://issues.apache.org/jira/browse/NIFI-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Rosander updated NIFI-3530:
---------------------------------
    Description: 
PutHiveStreaming doesn't always pass the HiveConf object down to the Hive api when it is needed.  This causes problems with a kerberized or otherwise non-default setup.

Workaround for site xmls is to put them into NiFi's conf directory (so they'll be on the classpath) and clear the box for site xmls on the processor.

  was:PutHiveStreaming doesn't always pass the HiveConf object down to the Hive api when it is needed.  This causes problems with a kerberized or otherwise non-default setup.


> PutHiveStreaming doesn't fully utilize *-site.xml files
> -------------------------------------------------------
>
>                 Key: NIFI-3530
>                 URL: https://issues.apache.org/jira/browse/NIFI-3530
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Bryan Rosander
>            Assignee: Bryan Rosander
>             Fix For: 1.2.0
>
>
> PutHiveStreaming doesn't always pass the HiveConf object down to the Hive api when it is needed.  This causes problems with a kerberized or otherwise non-default setup.
> Workaround for site xmls is to put them into NiFi's conf directory (so they'll be on the classpath) and clear the box for site xmls on the processor.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)