Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.38.0
Description
LoptOptimizeJoinRule uses costs comparisons to recursively decide whether to add a join at the top of the joins tree or to push it down.
When doing so, instead of directly calling mq.getCumulativeCost(rel), it should rely on call.getPlanner.getCost(rel, mq), which will be used thereafter to choose the best joins tree.
This way, it becomes possible to customize the costs computation during the heuristic joins ordering phase by just overriding the getCost() method of the optimization planner.
Without this patch, it is only possible to alter joins costs at the final phase of the algorithm, which defeats the goal of customizing them, including during the to-top/push-down phase.
Attachments
Issue Links
- is related to
-
CALCITE-7093 DPhyp algorithm should accept cost model as parameter
-
- Open
-
- links to