[
https://issues.apache.org/jira/browse/NIFI-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420028#comment-15420028
]
ASF GitHub Bot commented on NIFI-2553:
--------------------------------------
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/843
@YolandaMDavis Thanks for reviewing and testing! After looking at the
existing EL validator in StandardValidators, it wasn't used by any processor
and I believe the logic didn't fully make sense. It was saying "if a property
supports EL and EL is present, return true" but this doesn't mean the EL was
valid.
So I replaced it with the logic from the validator in the abstract hadoop
processor which I believe is correct... "if EL is supported and EL is present,
check if all expressions are valid and return true if they are, otherwise
return the message about what wasn't valid. If EL is not supported, or if EL is
not present, return true"
> HDFS processors throwing exception from OnSchedule when directory is an
> invalid URI
> -----------------------------------------------------------------------------------
>
> Key: NIFI-2553
> URL: https://issues.apache.org/jira/browse/NIFI-2553
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.0.0, 0.7.0
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
> Fix For: 1.0.0
>
>
> 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:
> {code}
> 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() });
> {code}
> 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).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
