Joseph Percivall created NIFI-5165:
--------------------------------------
Summary: PutElasticsearchHttp error handling doesn't properly
extract ES6 error reason
Key: NIFI-5165
URL: https://issues.apache.org/jira/browse/NIFI-5165
Project: Apache NiFi
Issue Type: Improvement
Affects Versions: 1.6.0
Reporter: Joseph Percivall
In the event the overall call "succeeds" but a FlowFile within the batch fails
(leading to the error handling here[1]), the error handling doesn't properly
pull out the error reason. An example of such error in ES 6:
{quote}{
"took": 0,
"ingest_took": 0,
"errors": true,
"items": [
{
"index": {
"_index": "theIndex",
"_type": "theType",
"_id": null,
"status": 400,
"error": {
"type": "illegal_argument_exception",
"reason": "pipeline with id [thePipeline] does not exist"
}
}
}
]
{quote}
The problem is the extra nesting of "index" which is not accounted for.
[1]
https://github.com/apache/nifi/blob/4df3eb567d8dff396b0e2380949e971d074dd04b/nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/PutElasticsearchHttp.java#L367
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
