[ https://issues.apache.org/jira/browse/NIFI-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503172#comment-16503172 ]
ASF GitHub Bot commented on NIFI-5145: -------------------------------------- Github user MikeThomsen commented on the issue: https://github.com/apache/nifi/pull/2749 @markap14 can you review? Since you brought this up on the dev list, here's the simple summary: The test framework is too strict on processors where input is optional. In those cases, it's common to just call `evaluateExpressionLanguage` with a null flowfile, but the test framework won't allow that. So it reports false negatives on execution that would go through with live execution of the processors. > 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)