[jira] [Commented] (NIFI-11111) Allow output of Elasticsearch error responses from REST API based PutElasticsearch processors

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on NIFI-11111:
--------------------------------------------------------

Commit 05418d94f0d75513e3471032d872fd417242329f in nifi's branch refs/heads/main from Chris Sampson
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=05418d94f0 ]

NIFI-11111 add option to output Elasticsearch error responses as FlowFile to PutElasticsearchJson and PutElasticsearchRecord
NIFI-11111 clarify error_responses relationships in PutElasticsearchJson/Record processors
NIFI-11111 Refactor exception handling for error response flowfile transfer
NIFI-11111 Add elasticsearch.bulk.error attributes containing the Elasticsearch _bulk response for error documents in PutElasticsearchJson

This closes #6903

Signed-off-by: Mike Thomsen <mt...@apache.org>


> Allow output of Elasticsearch error responses from REST API based PutElasticsearch processors
> ---------------------------------------------------------------------------------------------
>
>                 Key: NIFI-11111
>                 URL: https://issues.apache.org/jira/browse/NIFI-11111
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Chris Sampson
>            Assignee: Chris Sampson
>            Priority: Major
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> {{PutElasticsearchJson}} and {{PutElasticsearchRecord}} both allow the logging of the Elasticseach Bulk API responses when there are {{errors}} (or {{not_found}} status if enabled in the processor properties).
> They also (optionally) output the FlowFile documents/Records that caused the errors/not_found status (by matching the index of the error/not_found responses to the input FlowFile(s)/Record(s)).
> However, viewing the NiFi logs is not always easy in some environments and matching the NiFi FlowFile/Record to the Elasticsearch error response can be difficult.
> Adding the ability to output the Elasticsearch error/not_found responses (as enabled within the NiFi processors) would help NiFi users debug issues with data sent to Elasticsearch.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)