You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/11/22 17:56:58 UTC

[jira] [Commented] (NIFI-3082) PutElasticsearchHttp fails to dequeue item on 5xx response

    [ https://issues.apache.org/jira/browse/NIFI-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15687417#comment-15687417 ] 

ASF GitHub Bot commented on NIFI-3082:
--------------------------------------

GitHub user mattyb149 opened a pull request:

    https://github.com/apache/nifi/pull/1258

    NIFI-3082: Fixed status code handling in PutElasticsearchHttp

    For consistency, the status code handling is now the same as FetchElasticsearchHttp with respect to status codes and transfer relationships.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mattyb149/nifi NIFI-3082

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/1258.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1258
    
----
commit ef04a496c2c6bc51d02ba025954ca1d98698515c
Author: Matt Burgess <ma...@apache.org>
Date:   2016-11-22T17:53:45Z

    NIFI-3082: Fixed status code handling in PutElasticsearchHttp

----


> PutElasticsearchHttp fails to dequeue item on 5xx response
> ----------------------------------------------------------
>
>                 Key: NIFI-3082
>                 URL: https://issues.apache.org/jira/browse/NIFI-3082
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.0.0
>            Reporter: Carson Gaspar
>            Assignee: Matt Burgess
>
> When Elasticsearch returns a 5xx response (e.g. when a field doesn't match the index format), PutElasticsearchHttp does not dequeue the item, causing it to infinitely retry and cause a backlog.
> Expected behaviour would be to route the item to either the retry or failed outputs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)