Remove field_stats pre-flight option for index patterns #12814
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This feature was originally added to make searches against Elasticsearch more performant when searching across many indices, such as when dealing with daily indices that have accumulated for years. Elasticsearch now automatically optimizes index access once a certain amount of shards are in play, so Kibana doesn't need to hack its own solution. This option can be removed entirely as existing index patterns that had this option configured will degrade gracefully.
|
w00t |
This was referenced Jul 21, 2017
No need to use Field Stats API in the dashboard and visualise tabs (and possibly Discover too)
#6644
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This feature was originally added to make searches against Elasticsearch
more performant when searching across many indices, such as when dealing
with daily indices that have accumulated for years. Elasticsearch now
automatically optimizes index access once a certain amount of shards are
in play, so Kibana doesn't need to hack its own solution.
This option can be removed entirely as existing index patterns that had
this option configured will degrade gracefully.
Closes #12736