-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Auto-completion wrongly suggesting size field when using terms agg within composite agg #120512
Conversation
@elasticmachine merge upstream |
Pinging @elastic/kibana-stack-management (Team:Stack Management) |
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.
Hi @vladpro25, thank you so much for opening this PR!
If I understand correctly, your suggested change will remove size
parameter from terms
aggregation. But the linked issue requests to remove size
fromterms
aggregation only when it's used as a source in composite
aggregation. Could you please confirm with the Elasticsearch team that size
parameter can't be used when terms
is a source for composite
aggregation? I was not able to find this in the docs.
Terms aggregation docs
Composite aggregation docs
💚 Build Succeeded
Metrics [docs]
To update your PR or re-run it, just comment with: cc @vladpro25 |
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.
@vladpro25 it's definitely wrong fix. size
should be reverted for terms
aggregation.
@yuliacech I've tried execute composite
aggregation locally and looks like ES doesn't supports that case:
But not sure that it's too easy to understand that we are inside of composite agg. @vladpro25 let's discuss it offline tomorrow
Thanks for checking this, @alexwizp! I opened this docs issue elastic/elasticsearch#81431 to add this information to the Elasticsearch guide. |
Hi @vladpro25, the current assumption in the code is that aggregations behave the same when used alone and when used as a source for other aggregations, like |
Closes: #53112
Describe the issue:
[Console] Auto-completion wrongly suggesting size field when using terms agg within composite agg
Steps to reproduce
Using Dev Tools autocomplete:
(e.g., follow this tutorial: https://www.elastic.co/blog/composite-aggregations-elasticsearch-pizza-delivery-metrics)
Final result
terms aggregation within composite aggregation does not allow for size field.
Confirmation