-
Notifications
You must be signed in to change notification settings - Fork 24.7k
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
[DOCS] Adds size parameter details to aggregating data for faster performance page #93475
Conversation
Documentation preview: |
@@ -34,6 +34,10 @@ to match. For example, if you use a `max` aggregation on a time field called | |||
descending order. Additional `composite` aggregation value sources are allowed, | |||
such as `terms`. | |||
|
|||
* The `size` parameter of the non-composite aggregations must be configured |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
must be configured properly to match
Could we just say "must match" instead?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment, otherwise LGTM
Pinging @elastic/ml-core (Team:ML) |
Pinging @elastic/es-docs (Team:Docs) |
@elasticsearchmachine test this please |
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
…formance page (elastic#93475) (cherry picked from commit 9229011)
…formance page (elastic#93475) (cherry picked from commit 9229011)
Overview
This PR adds a recommendation for using the
size
parameter in a non-composite aggregation.Preview
Aggregations