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.

Sign up for GitHub

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

Jump to bottom

Investigate how to use HepPlanner + VolcanoPlanner in order to speed up simple queries #652

Open
eolivelli opened this issue Jul 7, 2020 · 0 comments
Open

Investigate how to use HepPlanner + VolcanoPlanner in order to speed up simple queries #652

eolivelli opened this issue Jul 7, 2020 · 0 comments
Labels
component/calcite component/core enhancement

Comments

@eolivelli
Copy link
Contributor

We are currently (0.16.x) using only VolcanoPlanner to perform data access planning.

It is very common among Calcite users to split the planning phase into to cycles:

  • with HepPlanner (rule based planner) simplify the query
  • with VolcanoPlanner (cost based planner) find the best execution plan

This way we could have a faster SQL planning especially for simple queries.

Another action we could explore is to prune a few rules from VolcanoPlanner or make some "sql-complexity level" configuration, advanced users will use the full ruleset.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/calcite component/core enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@eolivelli @aluccaroni