[
https://issues.apache.org/jira/browse/NIFI-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510162#comment-16510162
]
ASF GitHub Bot commented on NIFI-5145:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2749
What is the current state of this PR? The tests are passing but they were
before that. Does ListFTP or some processor break without this fix? If not, one
comment above implies something would be broken without another Jira/PR on its
heels. I thought because of the issue between FTPTransfer and ListFTP's
properties, the flow file attributes won't be honored?
> MockPropertyValue.evaluateExpressionLanguage(FlowFile) cannot handle null
> inputs
> --------------------------------------------------------------------------------
>
> Key: NIFI-5145
> URL: https://issues.apache.org/jira/browse/NIFI-5145
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Mike Thomsen
> Assignee: Mike Thomsen
> Priority: Major
> Fix For: 1.7.0
>
>
> The method mentioned in the title line cannot handle null inputs, even though
> the main NiFi execution classes can handle that scenario. This forces hack to
> pass testing with nulls that looks like this:
> String val = flowFile != null ?
> context.getProperty(PROP).evaluateExpressionLanguage(flowfile).getValue() :
> context.getProperty(PROP).evaluateExpressionLanguage(new
> HashMap()).getValue();
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
