[
https://issues.apache.org/jira/browse/NIFI-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Gresock updated NIFI-7036:
---------------------------------
Description:
One use case that isn't supported by the current implementation of query-info
and "no hits" being returned by QueryElasticsearchHttp is when you want to be
able to check if there are hits in ES without overwriting the contents of the
flow file. Currently if your search returns with no hits, this fact is only
reported in the query-info relationship, which does not have the contents of
the incoming flow file.
I propose adding a value to "Routing Strategy for Query Info" called "Append as
Attributes", which will simply add the query info attributes (es.query.url and
es.query.hitcount) to the incoming flow file (which is routed to success,
retry, or failure) instead of being added to flowfile that goes to the
query-info relationship.
was:
One use case that isn't supported by the current implementation of query-info
and "no hits" being returned by QueryElasticsearchHttp is when you want to be
able to check if there are hits in ES without overwriting the contents of the
flow file. Currently if your search returns with no hits, this fact is only
reported in the query-info relationship, which does not have the contents of
the incoming flow file.
I propose adding a value to "Routing Strategy for Query Info" called "Append as
Attributes", which will simply add the query info attributes (es.query.url and
es.query.hitcount) to the normal flow file (which is routed to success, retry,
or failure) instead of being added to flowfile that goes to the query-info
relationship.
> Add QueryElasticsearchHttp property to support no hits on original FF
> ---------------------------------------------------------------------
>
> Key: NIFI-7036
> URL: https://issues.apache.org/jira/browse/NIFI-7036
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joseph Gresock
> Assignee: Joseph Gresock
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> One use case that isn't supported by the current implementation of query-info
> and "no hits" being returned by QueryElasticsearchHttp is when you want to be
> able to check if there are hits in ES without overwriting the contents of the
> flow file. Currently if your search returns with no hits, this fact is only
> reported in the query-info relationship, which does not have the contents of
> the incoming flow file.
> I propose adding a value to "Routing Strategy for Query Info" called "Append
> as Attributes", which will simply add the query info attributes (es.query.url
> and es.query.hitcount) to the incoming flow file (which is routed to success,
> retry, or failure) instead of being added to flowfile that goes to the
> query-info relationship.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
