[ https://issues.apache.org/jira/browse/NIFI-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476323#comment-16476323 ]
ASF GitHub Bot commented on NIFI-5145: -------------------------------------- Github user MikeThomsen commented on the issue: https://github.com/apache/nifi/pull/2672 @mattyb149 I just changed the override to be the one without a parameter. I agree that there should be a task for squashing the scope bugs, but do the few that got squashed here need to be cherry picked out or should they just stay in? > 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)