You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/06/01 12:55:00 UTC

[jira] [Commented] (NIFI-5145) MockPropertyValue.evaluateExpressionLanguage(FlowFile) cannot handle null inputs

    [ https://issues.apache.org/jira/browse/NIFI-5145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16497951#comment-16497951 ] 

ASF GitHub Bot commented on NIFI-5145:
--------------------------------------

Github user MikeThomsen commented on the issue:

    https://github.com/apache/nifi/pull/2749
  
    @joewitt can you review this commit?


> 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)