Record Rejected by Elasticsearch [error type]: mapper_parsing_exception [reason]: 'failed to parse field [xyz] of type [text] in document with id

[vishalmamidi1]

(check apply)

• [*] read the contribution guideline

Save Rejected by Elasticsearch record to another Indice without loosing data

I always get exceptions from Fluentd like the below

1: Rejected by Elasticsearch [error type]: mapper_parsing_exception  [reason]: 'failed to parse field [xyz] of type [text] in document with id

2: Rejected by Elasticsearch [error type]: mapper_parsing_exception  [reason]: 'failed to parse field [xyz] of type [boolian] in document with id

3: Rejected by Elasticsearch [error type]: mapper_parsing_exception  [reason]: 'failed to parse field [xyz] of type [long] in document with id

4: Rejected by Elasticsearch [error type]: illegal_argument_exception [reason]: 'Rejecting mapping update to [java-2022.03] as the final mapping would have more than 1 type: [_doc, fluentd]

Always such exceptions are related to my current index template which my data is going to

solution I like

It's harder to go to Fluentd POD and check every time and data which got rejected I gone and I cannot retrieve it.

what if we can store such rejected data to another index, where my log which got rejected by OpenSearch is not completely gone.

alternatives I've considered

Alternatives I considered are logging Fluentd logs to a separate index where I can see whether, any record got rejected but in this case, I can say data got rejected but cannot retrieve original rejected data.

[github-actions[bot]]

@vishalmamidi1 this issue was automatically closed because it did not follow the issue template.