[
https://issues.apache.org/jira/browse/NIFI-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905196#comment-15905196
]
ASF GitHub Bot commented on NIFI-3574:
--------------------------------------
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/1578#discussion_r105409335
--- Diff:
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/util/hive/HiveConfigurator.java
---
@@ -74,7 +74,8 @@ public HiveConf getConfigurationFromFiles(final String
configFiles) {
public void preload(Configuration configuration) {
try {
- FileSystem.get(configuration);
+ FileSystem.get(configuration).close();
--- End diff --
Did you test this with respect to why this line was added in the first
place (High Availability clusters I think)? Just wanted to make sure it
wouldn't introduce a regression.
> PutHiveStreaming affected by UserGroupInformation static side effects
> ----------------------------------------------------------------------
>
> Key: NIFI-3574
> URL: https://issues.apache.org/jira/browse/NIFI-3574
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Bryan Rosander
> Assignee: Bryan Rosander
>
> Currently if you point a PutHiveStreaming processor at a secure cluster,
> start it, stop it, and then reconfigure it to point at a different unsecured
> cluster, some state from the first connection is used by the underlying Hive
> and Hadoop libraries when attempting to connect to the second cluster.
> This can be mitigated by ensuring that the
> UserGroupInformation.setConfiguration() method is used in onSetup() and that
> the approprate UserGroupInformation instance is used in ugi.doAs calls.
> In order to isolate multiple PutHiveStreaming processors, a
> RequiresInstanceClassLoading annotation should be added to the processor.
> This should insulate it from other static side effects.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
