elastic / elastic/logstash

logstash illegal_argument_exception reasons can be unclear

Open
#5,671 0 comments 1 reaction 0 assignees View on GitHub
Dominant language
Java
Stars
14.9k
Forks
3.5k
Avg merge
19h 14m
Merged PRs (30d)
63

Description

- Version:
logstash 2.2.4
- Operating System:
centos7 64
- Config File (if you have sensitive info, please remove it):
`
filter {
xml {
source => "message"
target => "testsuites"
store_xml => true
}
}
`
- Sample Data:

```








```
- Steps to Reproduce:
create an index with a `testsuite` string field.
send that xml file to logstash (i'm using http input plugin)

the testsuite field collides because it's already a string and can't be a nested field.
logstash gives less than helpful error (logstash.log):

```
"status"=>400, "error"=>{"type"=>"mapper_parsing_exception", "reason"=>"failed to parse [data]", "caused_by"=>{"type"=>"illegal_argument_exception", "reason"=>"unknown property [testsuite]"}}}}, :level=>:warn}
```

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.