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

Document the default max number of buckets in the auto_date_histogram documentation #32950

Closed
colings86 opened this issue Aug 17, 2018 · 3 comments
Assignees
Labels
:Analytics/Aggregations Aggregations >docs General docs changes Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) Team:Docs Meta label for docs team

Comments

@colings86
Copy link
Contributor

colings86 commented Aug 17, 2018

Document that max_bucket setting means that by default the max number of buckets you can request in the auto_date_histogram aggregation is 333.

This is because we need collect num_buckets * 30 buckets before we can merge up to the next interval

We should also mention that this limit can be changed using the max_buckets setting

@colings86 colings86 added >docs General docs changes :Analytics/Aggregations Aggregations labels Aug 17, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search-aggs

@debadair
Copy link
Contributor

[doc issue triage]

See discussion in #28993.

@rjernst rjernst added Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) Team:Docs Meta label for docs team labels May 4, 2020
@not-napoleon
Copy link
Member

I think we can close this now that we've resolved #57042, which causes max buckets to only be checked during the reduce phase. Feel free to reopen if there's a need, but it seems redundant to me at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/Aggregations Aggregations >docs General docs changes Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) Team:Docs Meta label for docs team
Projects
None yet
Development

No branches or pull requests

6 participants