[
https://issues.apache.org/jira/browse/NIFI-7036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17018954#comment-17018954
]
ASF subversion and git services commented on NIFI-7036:
-------------------------------------------------------
Commit e51ab8c9d6b678dc4e9549562d7c9f58f0445a04 in nifi's branch
refs/heads/master from Joe Gresock
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e51ab8c ]
NIFI-7036: This closes #3993. Adding 'Append to Attributes' to
QueryElasticsearchHttp
Signed-off-by: Joe Witt <[email protected]>
> 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
> Fix For: 1.11.0
>
> 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)