Skip to content
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

Dynamic Mappings set to false on index templates despite showing true in the UI #203112

Open
CarsonHrusovsky opened this issue Dec 4, 2024 · 3 comments

Comments

@CarsonHrusovsky
Copy link

Elasticsearch Version

8.16.1

Installed Plugins

No response

Java Version

23.0.0.0

OS Version

Windows Server 2019 1809

Problem Description

I first noticed this in the logs-endpoint.events.process index template (but I doubt this is just an endpoint issue). Within the Managed Index Template, dynamic mappings is set to "false". Before updating to 8.16.1 this was set to "true" and has thus broken our dynamic mappings we were relying on. Regardless of this - the true issue is the fact that mappings are set to false in this template despite this clearly showing when investigating the UI.

"mappings": { "dynamic": "false", "_meta": { "managed_by": "fleet", "managed": true, "package": { "name": "endpoint" } },

Image

If I were to toggle this off and then on again, the preview will show this.

"mappings": { "dynamic": "true", "_meta": { "managed_by": "fleet", "managed": true, "package": { "name": "endpoint" } },

This seems like a bug. Additionally, the replacement of dynamic mappings from 'true' to 'false' here is very frustrating as dynamic mappings is configured for this index template under the ecs@mappings component template, but isn't enabled by default.

Steps to Reproduce

My steps to recreate was to update to 8.16.1 from 8.15.2. I would guess this is default behavior for this index template - but I am not without a doubt sure of this.

Logs (if relevant)

No response

@nicpenning
Copy link

Related: #150395 ?

@PeteGillinElastic
Copy link
Member

Thanks for the report. It sounds like the first issue here is that the kibana UI is showing dynamic mappings as enabled, when the API shows them as disabled. That seems like a kibana issue rather than an elasticsearch issue, so I'm going to transfer this to the kibana repo for them to investigate. (If there is an ES issue then the kibana team will obviously report that to us.)

@PeteGillinElastic PeteGillinElastic transferred this issue from elastic/elasticsearch Dec 5, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Dec 5, 2024
@nicpenning
Copy link

Should the managed templates for this and other elastic Defend integrations be set to dynamic mapping: true? It is concerning if something is forcing these to be dynamic mapping off.

@botelastic botelastic bot removed the needs-team Issues missing a team label label Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants