You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2018/11/09 16:42:00 UTC
[jira] [Updated] (NIFI-5809) QueryRecord stops processing data if
selecting only a single field and that field is null
[ https://issues.apache.org/jira/browse/NIFI-5809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Payne updated NIFI-5809:
-----------------------------
Assignee: Mark Payne
Affects Version/s: 1.9.0
Status: Patch Available (was: Open)
> 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)