Skip to content
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

Optimize filters execution another way #88660

Open
nik9000 opened this issue Jul 20, 2022 · 1 comment
Open

Optimize filters execution another way #88660

nik9000 opened this issue Jul 20, 2022 · 1 comment
Labels
:Analytics/Aggregations Aggregations >enhancement Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo)

Comments

@nik9000
Copy link
Member

nik9000 commented Jul 20, 2022

Description

Back when I was working on #74260 I investigated another way of processing the filters agg by iterating the main query and the filters clauses in something similar feeling to DisjunctionScorer that could remember which queries matched. I ultimately abandoned it because it was slower than the "native" terms and range agg, but it was much faster than trying to execute either the filter by filter with very complex queries or the "compatible" mode for the terms agg. It should be possible to bring that back, though I don't have the code anymore. If we find ourselves running frequently having to evaluate filters aggs at the top level that can not be otherwise rewritten into filter-by-filter, this could be a useful middle ground.

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-analytics-geo (Team:Analytics)

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

No branches or pull requests

3 participants