[
https://issues.apache.org/jira/browse/NIFI-3576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419160#comment-16419160
]
Luis Pallares commented on NIFI-3576:
-------------------------------------
>would every flow file have a 'es.hits.total' and maybe a 'es.hit.number'?
yes, 'es.hits.total' to keep the ES convention for this field.
> just empty to a new relationship?
it would be great to have a "not found" relationship when 'es.hits.total' is 0,
if not, I bet developers will be using an "evaluator" connected to a "router"
to make it usable, hence my advice to use a new rel to have the (if not results
then) implicitly done by the processor.
> What would the flow file output be?
> empty to success with the attributes?
flowfile is OK as it is, later we can work on a QueryElasticsearchRecord now
that everything trends to the record-oriented methodology which is great.
thanks.
> 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
> 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)
