Increase search.max_bucket default value by one #70645
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
|
Pinging @elastic/es-analytics-geo (Team:Analytics) |
|
Lgtm
…On Mon, Mar 22, 2021, 10:25 Elastic Machine ***@***.***> wrote:
Pinging @elastic/es-analytics-geo
<https://github.com/orgs/elastic/teams/es-analytics-geo> (Team:Analytics)
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
<#70645 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABUXIQXDQEWQUMJASUDJ33TE5HM3ANCNFSM4ZTG7PZQ>
.
|
iverase
added a commit
that referenced
this pull request
Mar 23, 2021
jrodewig
added a commit
that referenced
this pull request
Jun 29, 2021
jrodewig
added a commit
that referenced
this pull request
Jun 29, 2021
jrodewig
added a commit
that referenced
this pull request
Jun 29, 2021
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.
In #57042, the default value for search.max_bucket was increased to 65,535. Unfortunately this value is short by one for some geo aggregations. For example if you want to aggregate on a geo tile with a scaling factor of 8, it means that you might be generating 256 * 256 buckets, which is one more than the default.
This PR increase the default by one (65,536).