Description
Currently the query like follow requires too mush time to optimise (> 5 minutes on my laptop):
select * from t1 inner join t2 on t1.id = t2.id where t1.val1 > 0 or t1.val2 > 10
The reason is that every step of push down of the filter creates one more valid plan, that in conjunction with OrToUnion rule and all those Join's traits propagation significally boosts the search space.
We could take an advantage of heuristic planner here to push down filters as close to the leaf as possible, whereas pruning all alternative plans.
Attachments
Issue Links
- causes
-
IGNITE-15235 Calcite. Unignore or remove tableSpoolBroadcastNotRewindable test
- Resolved
- fixes
-
IGNITE-14721 Calcite. SOME with subquery consume huge time.
- Resolved
- is part of
-
IGNITE-12248 Apache Calcite based query execution engine
- Open
- links to