Use dynamic: false for config saved object mappings #70436
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Reduces the field count by specifying
dynamic: false
for the config saved object type. We need to be able to store arbitrary fields in the config saved object type, but we only ever sort on thebuildNum
. Since every "advanced setting" that's changed from the default adds a field, this can add as many as 78 fields onmaster
and even more for users who have config objects from previous Kibana releases.Related to #43673
Checklist
Delete any items that are not applicable to this PR.
For maintainers