mirror of
https://github.com/rsyslog/rsyslog.git
synced 2025-12-21 11:20:42 +01:00
eb11580336
Write all of the original request metadata fields to $.omes for the retry, if present. This may include all of the following: _index, _type, _id, _parent, pipeline This is in addition to the fields from the response. If the same field name exists in the request metadata and the response, the field from the request will be used, in order to facilitate retrying the exact same request. Have to set a tag with `MsgSetTAG` to avoid a UBSAN error.
How to access ElasticSearch on local machine (for testing):
===========================================================
see: https://github.com/mobz/elasticsearch-head
How to produce an error:
========================
It's quite easy to get 400, if you put a wrong mapping to your
index. That would be easy to reproduce in "normal" omelasticsearch usage
conditions, by only altering the ES configuration:
1. Make your index first. Let's call it "testindex":
$ curl -XPUT localhost:9200/testindex/
2. Put your mapping for a search type called "mytype", where you specify
that date property should be an integer:
$ curl -XPUT localhost:9200/testindex/mytype/_mapping -d '{"mytype":{"properties": {"timegenerated":{"type":"integer"}}}}'
3. Now try to insert something where date is not an integer:
$ curl -XPOST localhost:9200/testindex/mytype/ -d '{"timegenerated":"bla"}'
{"error":"MapperParsingException[Failed to parse [date]]; nested: NumberFormatException[For input string: \"bla\"]; ","status":400}