[ https://issues.apache.org/jira/browse/NIFI-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16479984#comment-16479984 ]
ASF subversion and git services commented on NIFI-5145: ------------------------------------------------------- Commit 29e96ed0e0b63bc2f5b0f07751fe7efbc10f18ab in nifi's branch refs/heads/master from [~ca9mbu] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=29e96ed ] NIFI-5145: Fixed MockPropertyValue to call the correct evaluateAttributeExpressions when FF is null Signed-off-by: Matthew Burgess <mattyb...@apache.org> This closes #2717 > 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)