[
https://issues.apache.org/jira/browse/NIFI-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419537#comment-16419537
]
Otto Fowler commented on NIFI-3576:
-----------------------------------
I agree that it is valid to return no hits, if this were returning all hits as
one OR one flow file per hit you can imagine just outputting "\{"hits":[]}.
Since this outputs a file per hit, what the attributes would be on the 'empty'
FF is where I'm left wondering. I would think that doing hit.number,
nit.total ( so 1 of 20 ) etc, like segment numbers would work ( and make sense
if you did get hits as well).
I think 1 is a valid step.
Instead of 2 or 3, I was thinking it would be better to have a REL_QUERY_INFO,
that had the query as the document, and the hits etc as attributes.
> QueryElasticsearchHttp should have a "Not Found"/"Zero results" relationship
> ----------------------------------------------------------------------------
>
> Key: NIFI-3576
> URL: https://issues.apache.org/jira/browse/NIFI-3576
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joseph Percivall
> Assignee: Otto Fowler
> Priority: Minor
>
> In the event of a successful call, QueryElasticsearchHttp always drops the
> incoming flowfile and then emits pages of results to the success
> relationship. If the search returns no results then no pages of results are
> emitted to the success relationship.
> The processor should offer other options for handling when there are no
> results returned.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
