Skip to content

Allows for a composite aggregation to be a child of a filter aggregation #38863

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

Closed

Conversation

juliovalcarcel
Copy link

A composite aggregation should be allowed to be a grandchild of a nested aggregation only if it's parent is a filter aggregation.

A nested aggregation has no way to filter a list of nested documents like you do when the composite is the top level aggregation.

Relates to #37178

A composite aggregation should be allowed to be a grandchild of a nested
aggregation only if it's parent is a filter aggregation.

Relates to #37178
@juliovalcarcel
Copy link
Author

CC: @jimczi

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-analytics-geo

@juliovalcarcel
Copy link
Author

Hey @polyfractal / @jimczi the cla is signed now, but it doesn't appear to be updated. Is there something else I have to do?

@polyfractal
Copy link
Contributor

Heya @juliovalcarcel, just chatted with our infra. Looks like you signed right when the clachecker was down for a change, so the signature slipped into the aether.

Would you mind signing again? Sorry for the hassle!

@juliovalcarcel
Copy link
Author

@polyfractal resigned

@polyfractal
Copy link
Contributor

Awesome, thanks @juliocamarero. Change looks fine to me, but I only have some experience with composite agg so we should wait for @jimczi too.

Could you add a test to verify this works as expected?

@juliocamarero
Copy link
Member

wrong julio? @juliovalcarcel :D

@polyfractal
Copy link
Contributor

Argh, sorry about that. 🤦‍♂️

@juliovalcarcel
Copy link
Author

@polyfractal I am not all that familiar with the test framework and didn't see an existing test for the composite as a child of a nested. If you or @jimczi could help provide me some guidance on how to set up the test within the elastic test framework I would be more than happy too!

@javanna
Copy link
Member

javanna commented Mar 18, 2019

heya @juliovalcarcel sorry for keeping you on hold. I think it would be great if you could add a unit test to CompositeAggregationBuilderTests which verifies the updated behaviour. If I understand correctly the updated is called when the builder.build method is called, that should be a good start. Let me know if you have any further question.

@rjernst rjernst added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label May 4, 2020
@akanthos
Copy link

Are there any news on this ticket? I was wondering if it's going to be merged soon, as filtering before using composite aggregations seems to be a very nice thing to have.
Are there any plans to merge it? Maybe some expected version that would support that?
@juliovalcarcel, @javanna

Thanks!

@jimczi
Copy link
Contributor

jimczi commented May 13, 2020

Are there any news on this ticket? I was wondering if it's going to be merged soon, as filtering before using composite aggregations seems to be a very nice thing to have.

The logic in the pr looks good but we need a test. Apologize for missing the ping but a rest test similar to 230_composite should be added to validate the logic.

@noah79
Copy link

noah79 commented Jan 15, 2021

Is this ever going to be merged?

@not-napoleon
Copy link
Member

I was working on merging this, which requires writing tests for it, and I think I found an issue with the PR as it stands. I think the current implementation allows multiple levels of nested aggs before the composite, but the proposed change would only allow a single level. Should be fixable, but I don't expect to get to it soon.

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

Successfully merging this pull request may close these issues.

10 participants