[
https://issues.apache.org/jira/browse/NIFI-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618818#comment-17618818
]
Chris Sampson commented on NIFI-2958:
-------------------------------------
Suspect this is no longer an issue - I'm not sure which Elasticsearch
processors were being referred to here, but the mention of {{elasticsearch1.1
nar}} suggests these are very old processors that no longer exist in the NiFi
code base.
The (now deprecated) {{PutElasticsearchHttp}} and
{{PutElasticsearchHttpRecord}} both (optionally, if configured) check for
{{errors}} in the response and log the {{items}} therein.
Their respective replacement processors {{PutElasticsearchJson}} and
{{PutElasticsearchRecord}} both do the same thing, optionally also outputting
the {{input}} FlowFiles that caused Elasticsearch errors to an {{errors}}
relationship for further handling downstream within NiFi.
> Missing Error Message in PutElasticsearchHttp
> ---------------------------------------------
>
> Key: NIFI-2958
> URL: https://issues.apache.org/jira/browse/NIFI-2958
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Justin M Cavinee
> Priority: Minor
>
> Error messages are not being shown properly when the push to Elastic Search
> fails.
> When I get a failure, it just reads:
> Failed to Insert StandardFlowFileRecord[..] into Elastic Search due to ,
> transferring to failure.
> With nothing following the due to. If I use curl to directly push to content
> to ElasticSearch then I do get a proper error message, which should be put
> into the Elastic Search log.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
