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

Posted to issues@nifi.apache.org by "Joseph Gresock (Jira)" <ji...@apache.org> on 2021/04/06 12:33:00 UTC

[jira] [Resolved] (NIFI-8036) PutElasticsearchHttp could add failure reason as an attribute

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

Joseph Gresock resolved NIFI-8036.
----------------------------------
    Resolution: Not A Problem

This is OBE, per the PR comments

> PutElasticsearchHttp could add failure reason as an attribute
> -------------------------------------------------------------
>
>                 Key: NIFI-8036
>                 URL: https://issues.apache.org/jira/browse/NIFI-8036
>             Project: Apache NiFi
>          Issue Type: Improvement
>    Affects Versions: 1.12.1
>            Reporter: Joseph Gresock
>            Assignee: Joseph Gresock
>            Priority: Minor
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> When dealing with failures from PutElasticsearchHttp, we often find that we want to route based on the type of failure (e.g., parsing vs. communication).  Adding the failure reason as a flow file attribute to failed flow files would help a great deal.
> I propose adding the failure reason in the attribute "es.failure.reason".



--
This message was sent by Atlassian Jira
(v8.3.4#803005)