[
https://issues.apache.org/jira/browse/NIFI-2471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Moser updated NIFI-2471:
--------------------------------
Fix Version/s: 0.8.0
1.0.0
> 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)
