[NIFI-2553] HDFS processors throwing exception from OnSchedule when directory is an invalid URI

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Resolved
• Affects Version/s: 1.0.0, 0.7.0
• Fix Version/s: 1.0.0
• Assignee: Bryan Bende
• Reporter: Bryan Bende
• Created: 11/Aug/16 16:56
• Updated: 15/Aug/16 13:09
• Resolved: 15/Aug/16 13:09

Description

If you enter a directory string that results in an invalid URI, the HDFS processors will throw an unexpected exception from OnScheduled because of a logging statement on in AbstractHadoopProcessor:

getLogger().info("Initialized a new HDFS File System with working dir: {} default block size: {} default replication: {} config: {}",
                    new Object[] { fs.getWorkingDirectory(), fs.getDefaultBlockSize(new Path(dir)), fs.getDefaultReplication(new Path(dir)), config.toString() });

An example input for the directory that can produce this problem:
data_${literal('testing'):substring(0,4)%7D

In addition to this, FetchHDFS, ListHDFS, GetHDFS, and PutHDFS all create new Path instances in their onTrigger methods from the same directory, outside of a try/catch which would result in throwing a ProcessException (if it got past the logging issue above).

Issue Links

• links to: GitHub Pull Request #843