[jira] [Resolved] (NIFI-4331) Add "NotFound" route to QueryElasticsearchHttp

["Matt Burgess (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-4331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess resolved NIFI-4331.
--------------------------------
       Resolution: Duplicate
    Fix Version/s:     (was: 1.3.0)

Resolving this issue as a duplicate of NIFI-3576

> 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
>              Labels: features
>
> 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
(v7.6.3#76005)