Support sub aggregations on filter rewrite optimization #15253
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Follow up on filter rewrite optimization work. See: #13317, #13865, #14464.
The filter rewrite optimization path for aggregations is currently disabled when a sub aggregation is present. In this case we default back to the iterative doc values approach of collecting docs into our aggregation buckets.
This change adds support for sub aggregations by collecting doc ids into our sub aggregation while traversing the PointValues.PointTree. While we are still considering each doc id, we expect a modest performance boost using the PointValues.PointTree.
Related Issues
Resolves #[Issue number to be closed when this PR is merged]
#12602
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.