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/04/05 15:14:00 UTC

[jira] [Commented] (NIFI-6172) ElasticSearch StringLookupService always returns a value

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

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

Commit 4810f6d32e7f30763b22c704a65603120e4b3c54 in nifi's branch refs/heads/master from Mike Thomsen
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=4810f6d ]

NIFI-6172 Fixed a bug that caused ElasticSearchStringLookupService to always return a value even when it should return Optional.empty().

NIFI-6172 Fixed broken integration test.

Signed-off-by: Matthew Burgess <ma...@apache.org>

This closes #3399


> ElasticSearch StringLookupService always returns a value
> --------------------------------------------------------
>
>                 Key: NIFI-6172
>                 URL: https://issues.apache.org/jira/browse/NIFI-6172
>             Project: Apache NiFi
>          Issue Type: Bug
>            Reporter: Mike Thomsen
>            Assignee: Mike Thomsen
>            Priority: Major
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> The ElasticSearch StringLookupService always returns at least some sort of value even if the document is missing in ElasticSearch. That can cause it to break the contract behavior of LookupAttribute which expects to be able to filter null/missing values.



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