[
https://issues.apache.org/jira/browse/NIFI-2958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15690923#comment-15690923
]
Justin M Cavinee commented on NIFI-2958:
----------------------------------------
Looks like //error//reason is the right place (see the response below). Just
tested and this is still showing up as a blank error message in the log.
I didn't see anywhere to download the elasticsearch1.1 nar and I don't have my
build environment setup, assuming you've built it recently, can you send me the
nar? I've reproduced both the queuing error and the log message error, so I
just need to update the processor to test the fix.
Also, in addition to the elastic search error, I'm also seeing an
"IndexOutOfBoundsException", which might also be the reason the queue never
empties once it starts throwing exceptions.
{
"error" : {
"root_cause" : [
{
"type" : "mapper_parsing_exception",
"reason" : "object mapping for [interfaces] tried to parse field
[interfaces] as object, but found a concrete value"
}
],
"type" : "mapper_parsing_exception",
"reason" : "object mapping for [interfaces] tried to parse field
[interfaces] as object, but found a concrete value"
},
"status" : 400
}
> 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
(v6.3.4#6332)
