-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow index.mapping.ignore_malformed
to be set inside index templates
#730
Comments
@kcreddy thanks for opening the issue. To be sure I understand, the defaults for |
Hey @jsoriano
Yes, that seems to be the case. The source datastream and destination index has different
I think having a same value should help fix the issue. I agree to changing it to |
I think that is what we should do. The least surprising thing from a developer standpoint would be for any data streams or indices that get created through Fleet integrations to have similar configurations including |
Agree, opened issue in Kibana repo elastic/kibana#179445. And closing this one. Thanks! |
Currently for
elasticsearch_index_template
, only few properties are allowed to be set underindex.mapping
: https://github.com/elastic/package-spec/blob/main/spec/integration/data_stream/manifest.spec.yml#L211-L221We need to allow
index.mapping.ignore_malformed
to be set inside index templates.The issue without this property:
When a transform is involved, the source datastream (by default) contains
index.mapping.ignore_malformed: true
. This ingests any malformed documents, for example in: elastic/integrations#9360, a value of178.21.14.0/23
is ingested into the source datastream's fieldthreat.indicator.ip
. However, the transform crashes to index into the destination because (by default)index.mapping.ignore_malformed
isfalse
It is not possible to override this value as it follows the same index template definition.The text was updated successfully, but these errors were encountered: