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
Add reverse_nested
aggregation
#5507
Conversation
private final Filter parentFilter; | ||
private DocIdSetIterator parentDocs; | ||
|
||
// TODO: Should we add LongIntPagedHashMap? |
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.
I think it would make sense. Since all these paged impls are going to be very similar, I'm wondering how we could auto-generate them (just thinking out loud, this would need to be done in a separate change!)
…the next nested object mapping above the nested field specified in the `nested` agg wrapping the reverse_nested agg. Fail if reverse_nested agg isn't wrapped in a nested agg Rebased with master
Rebased and updated the PR:
|
aggregation can break out of the nested block structure and link to other nested structures or the root document, | ||
which allows nesting other aggregations that aren't part of the nested object in a nested aggregation. | ||
|
||
For example, lets say we have an index for a ticket system which issues and comments. The commends are inlined into |
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.
s/commends/comments/
Removed automatic path resolving If no path is defined then the reverse_nested agg always joins back to the root / main document level.
Updated the PR:
|
LGTM |
The `reverse_nested` aggregation allows to aggregate on properties outside of the nested scope of a `nested` aggregation. Closes #5507
PR for #5485
There a number of todos that need to be addressed.