[ https://issues.apache.org/jira/browse/NIFI-8036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Gresock updated NIFI-8036: --------------------------------- Status: Patch Available (was: Open) Patch available, fully tested in NiFi instance, works exactly to serve the intended purpose. > 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: 10m > 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)