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

Posted to issues@nifi.apache.org by "Daniel Stieglitz (Jira)" <ji...@apache.org> on 2026/03/17 20:06:00 UTC

[jira] [Resolved] (NIFI-12507) Update Documentation for PutHive3Streaming processor

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

Daniel Stieglitz resolved NIFI-12507.
-------------------------------------
    Resolution: Won't Do

The PutHive3Streaming is no longer part of NIFI.

> Update Documentation for PutHive3Streaming processor
> ----------------------------------------------------
>
>                 Key: NIFI-12507
>                 URL: https://issues.apache.org/jira/browse/NIFI-12507
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Arti Wadhwani
>            Priority: Trivial
>
> Customer did a first time implementation of PutHive3Streaming processor. Hive was using Kerberos authentication.
> We checked all processor properties and they looked correctly configured.
> – Manual kinit on the nifi nodes using same principal and keytab as configured in the processor, worked fine.
> – Verified that the hive-site.xml was in sync with the hive cluster
> Issue was finally resolved by setting "Hive Configuration Resources" property of PutHive3Streaming to use all three "hive-site.xml, core-site.xml and hdfs-site.xml". We believe this was due to Hive being kerberized and Namenode HA enabled.
> Can we update the document to use all 3 xml instead of just hive-site.xml in case of Kerberos and Namenode HA?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)