Phil Rogers created NIFI-4331: --------------------------------- Summary: Add "NotFound" route to QueryElasticsearchHttp Key: NIFI-4331 URL: https://issues.apache.org/jira/browse/NIFI-4331 Project: Apache NiFi Issue Type: New Feature Components: Extensions Affects Versions: 1.3.0 Environment: Linux Centos 7 Reporter: Phil Rogers Priority: Minor Fix For: 1.3.0
I have a need to check whether a record exists in Elasticsearch to decide what to do next. The attribute I need to check isn't a key in elasticsearch so I am using the QueryElasticsearchHttp to do the query. If the QueryElasticsearchHttp process experiences a not found on the query result the processor drops any further processing of that queued entry. It would be great if the QueryElasticsearchHttp processor could have a "not found" route added to it that way smarter logic could be applied Thanks in advance -- This message was sent by Atlassian JIRA (v6.4.14#64029)