[
https://issues.apache.org/jira/browse/NIFI-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475816#comment-16475816
]
ASF GitHub Bot commented on NIFI-5145:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2672
I think the invalid scopes thing should be done in a separate Jira, there
are more than just the ones above (~40 in total) so I think we should tackle
them all at once, and have this PR just call evaluateAttributeExpressions with
the empty map. I don't think that's a hack, it emulates the real behavior
(although the real one has a ValueLookup whose constructor skips flow file
processing if null).
> 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
>
> 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)
