[
https://issues.apache.org/jira/browse/NIFI-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406535#comment-15406535
]
ASF GitHub Bot commented on NIFI-2471:
--------------------------------------
GitHub user mosermw opened a pull request:
https://github.com/apache/nifi/pull/779
NIFI-2471 fix Hadoop configuration resources when talking to ...
…multiple Hadoop clusters
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mosermw/nifi NIFI-2471
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/779.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 #779
----
commit 873a7a747070284dbd72eaba49b5bc388c1c7a77
Author: Mike Moser <[email protected]>
Date: 2016-08-03T19:58:57Z
NIFIDEV-2471 fix Hadoop configuration resources when talking to multiple
Hadoop clusters
----
> Multiple Hadoop processors cannot point to different Hadoop clusters
> --------------------------------------------------------------------
>
> Key: NIFI-2471
> URL: https://issues.apache.org/jira/browse/NIFI-2471
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 0.7.0
> Reporter: Michael Moser
> Assignee: Michael Moser
> Priority: Minor
> Fix For: 1.0.0, 0.8.0
>
>
> Two GetHDFS processors, each with different Hadoop Configuration Resources,
> will only operate with one Hadoop cluster. In this specific case, both
> Hadoop clusters had the same HDFS system name. The AbstractHadoopProcessor
> disables caching of Configuration and FileSystem objects but it doesn't
> appear to be working.
> Also, if I configure a GetHDFS processor to point to one Hadoop cluster, but
> the processor is invalid because the Directory doesn't exist, the processor
> doesn't start (that's good). But if I change the Hadoop Configuration
> Resources to point to a different Hadoop cluster where the Directory does
> exist, then GetHDFS continues to talk to the first Hadoop cluster. It seems
> like the Configuration and FileSystem objects don't reset when I change the
> Hadoop Configuration Resources property.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
