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

["Pierre Villard (Jira)" <ji...@apache.org>]

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

Pierre Villard updated NIFI-11111:
----------------------------------
    Fix Version/s: 2.0.0
                   1.22.0
                       (was: 1.latest)
                       (was: 2.latest)

> 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
>             Fix For: 2.0.0, 1.22.0
>
>          Time Spent: 3.5h
>  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)