-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Disable dynamic mapping in .kibana #4964
Comments
👍 |
I'm not sure if we want to do this for 4.2.0? |
I think it would be fine to include in beta2, but not between beta2 and GA |
I'm voting to leave this for 4.3.0 I'm nervous about trying to jam this into 4.2.0 |
See @simianhacker for info on this. Assigning @LeeDr because the biggest impediment to doing this is tests. |
To prevent any possible mixups with existing indices, this should probably be dependent on the versioned indexes change. @rashidkpc Thoughts? |
I don't think so, no, there shouldn't be any problems with turning it on for new installations, or even old installations. Its mostly an enforcement method for plugins to force them to define their mapping ahead of time. |
And Kibana itself needs to explicitly define a mapping. I figured that may have unexpected consequences for people importing saved objects between versions and such. |
It shouldn't, it will just prevent objects that haven't had a mapping declared from being saved, but we declare mappings for all of our saved objects. |
Also if we include the mapping when the index is created then we won't have issue with the Global template. |
Yeah, but thats a bigger task, simply turning OFF dynamic mapping is a quick fix typo: changed on to off |
I don't understand exactly how this impacts tests and how I can test it.
And I thought you wanted to NOT have dynamic mapping. How is turning it ON a quick fix? |
@LeeDr fixed, that should've said "OFF" not "on". I'll assign this to myself and put in a pull that turns it OFF. Then jenkins can run the functional tests. As long as they pass we should be GTG |
Is this related? "Don't analyse title field in .kibana (or use multifield)" #4563 |
Having just run into an issue where the .kibana mappings were created incorrectly (since in my world everything is scripted via curl and nothing goes through the kibana UI) I would really like to see kibana installing these mappings the first time it runs. |
What the status of this? Need this also for v5.x |
In order to prevent future issues with mappings we should disable dynamic mapping in the .kibana index.
The text was updated successfully, but these errors were encountered: