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 subversion and git services (JIRA)" <ji...@apache.org> on 2019/03/20 01:32:00 UTC

[jira] [Commented] (NIFI-6127) AttributeExpressionLanguage - 'match' and 'find' throw NPE when comparison object is a non existing flowfile attribute

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

ASF subversion and git services commented on NIFI-6127:
-------------------------------------------------------

Commit 06f41ac6f8645fc2e37be2529200e89177f48197 in nifi's branch refs/heads/master from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=06f41ac ]

NIFI-6127: Fixed NPE in match() and find() EL functions when attribute doesn't exist

This closes #3378.

Signed-off-by: Koji Kawamura <ij...@apache.org>


> AttributeExpressionLanguage - 'match' and 'find' throw NPE when comparison object is a non existing flowfile attribute
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-6127
>                 URL: https://issues.apache.org/jira/browse/NIFI-6127
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Steven Youtsey
>            Assignee: Matt Burgess
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> MatchesEvaluator, line 56 - When the flow file attributes do not contain the attribute specified in the comparison portion of a 'matches' operation, the Pattern.compile(null) throws an NPE.
> Since there is no guarantee that a specified flow file attribute is present, this should simply return BooleanQueryResult(false) if the desired attribute does not exist.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)