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

Disable dynamic mapping in .kibana #4964

Closed
rashidkpc opened this issue Sep 16, 2015 · 16 comments
Closed

Disable dynamic mapping in .kibana #4964

rashidkpc opened this issue Sep 16, 2015 · 16 comments
Assignees
Labels
good first issue low hanging fruit release_note:enhancement Team:Operations Team label for Operations Team v5.5.0

Comments

@rashidkpc
Copy link
Contributor

In order to prevent future issues with mappings we should disable dynamic mapping in the .kibana index.

@spalger
Copy link
Contributor

spalger commented Sep 17, 2015

👍

@rashidkpc
Copy link
Contributor Author

I'm not sure if we want to do this for 4.2.0?

@spalger
Copy link
Contributor

spalger commented Sep 18, 2015

I think it would be fine to include in beta2, but not between beta2 and GA

@rashidkpc
Copy link
Contributor Author

I'm voting to leave this for 4.3.0 I'm nervous about trying to jam this into 4.2.0

@rashidkpc
Copy link
Contributor Author

See @simianhacker for info on this. Assigning @LeeDr because the biggest impediment to doing this is tests.

@epixa
Copy link
Contributor

epixa commented Mar 23, 2016

To prevent any possible mixups with existing indices, this should probably be dependent on the versioned indexes change. @rashidkpc Thoughts?

@rashidkpc
Copy link
Contributor Author

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.

@epixa
Copy link
Contributor

epixa commented Mar 23, 2016

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.

@rashidkpc
Copy link
Contributor Author

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.

@simianhacker
Copy link
Member

Also if we include the mapping when the index is created then we won't have issue with the Global template.

@rashidkpc
Copy link
Contributor Author

Yeah, but thats a bigger task, simply turning OFF dynamic mapping is a quick fix

typo: changed on to off

@LeeDr
Copy link

LeeDr commented Mar 23, 2016

Assigning @LeeDr because the biggest impediment to doing this is tests.

I don't understand exactly how this impacts tests and how I can test it.

Yeah, but thats a bigger task, simply turning on dynamic mapping is a quick fix

And I thought you wanted to NOT have dynamic mapping. How is turning it ON a quick fix?

@rashidkpc
Copy link
Contributor Author

@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

@tbragin
Copy link
Contributor

tbragin commented Jan 9, 2017

Is this related? "Don't analyse title field in .kibana (or use multifield)" #4563

@ctindel
Copy link

ctindel commented Jan 10, 2017

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.

@epixa epixa added Team:Operations Team label for Operations Team and removed discuss labels Jan 18, 2017
@Hronom
Copy link

Hronom commented Feb 3, 2017

What the status of this? Need this also for v5.x

@epixa epixa removed the P2 label Apr 25, 2017
@tbragin tbragin added the v5.5.0 label May 13, 2017
afgomez pushed a commit that referenced this issue Oct 30, 2019
Having a z-index adds problems with the stacking of the dropdowns when
there are two toolbars together.
afgomez pushed a commit that referenced this issue Oct 30, 2019
Having a z-index adds problems with the stacking of the dropdowns when
there are two toolbars together.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue low hanging fruit release_note:enhancement Team:Operations Team label for Operations Team v5.5.0
Projects
None yet
Development

No branches or pull requests

9 participants