[
https://issues.apache.org/jira/browse/NIFI-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16683268#comment-16683268
]
ASF subversion and git services commented on NIFI-5809:
-------------------------------------------------------
Commit 08189596d27af7bb4518646245549b480d4bb05a in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=0818959 ]
NIFI-5809: If QueryRecord has a single-column projection and that results in a
null value, do not confuse that with a null value being returned from the
Record Reader
This closes #3163.
Signed-off-by: Koji Kawamura <[email protected]>
> QueryRecord stops processing data if selecting only a single field and that
> field is null
> -----------------------------------------------------------------------------------------
>
> Key: NIFI-5809
> URL: https://issues.apache.org/jira/browse/NIFI-5809
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.9.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
>
> From the users@ mailing list, Mandeep Gill reported an issue where the
> following input to QueryRecord:
> \{"id": "129984bf31e025599c0e9232df5c7b7c", "price": 19.47}
> {"id": "a6cfcb7c7178b9d18c50f2f2dc41dab3", "price": null}
> Can cause problems with the following 2 queries:
> select count( *) from flowfile where price is null
> select price from flowfile
> I believe both of these queries are affected by the same issue: the query
> only looks at the "price" field and as soon as it encountered a null value
> there, it mistook that as a null record, meaning that it immediately throws
> out the record and thinks it's the end of the stream.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
