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
[feature request] Parent aggregation #9705
Comments
Can you please explain what is "high hanging fruit"? |
Hi @Kamapcuc good question :) it's not about priority, more about the effort required for the change. Low hanging fruits are easier to get than high hanging ones, that's it. Issues marked with the "high hanging fruit" label might require some refactoring on our end for instance, but that doesn't mean we make all of the easy changes first. |
Hi @martijnvg, now that the Parent/Child refactor was committed, do you think we can expect the Parent Aggregation in a near future? |
+1 |
is there any progress? |
Ok, i think it's time to start to contribute to the project )) |
I doubt this is ever going to come to pass. Closing |
Would love and need that, too! Maybe with the new ways of joining in elastic 6? |
Yeah, I miss this a lot as well, prevents us from switching from nested to parent/child for one of our large use-cases... |
I tried to implement the parent-aggregation and would like some feedback if the approach is correct, see #34210 |
Yeah, thanks you @centic9 ! :) |
For example, I have data:
So, I played 4 battles on American tanks and 2 on German tanks. I want to receive those data, when searching for battles. But I can do it only when I search for tanks:
Although, I can make such a monster:
But it's VERY uncomfortable and I must know all the terms of nation field. So, I'm asking for some kind of parent aggregation.
The text was updated successfully, but these errors were encountered: