[
https://issues.apache.org/jira/browse/IGNITE-15203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taras Ledkov updated IGNITE-15203:
----------------------------------
Labels: calcite (was: calcite3-required)
> Calcite. Extract Filter and Project related rules to separate HEP phase
> -----------------------------------------------------------------------
>
> Key: IGNITE-15203
> URL: https://issues.apache.org/jira/browse/IGNITE-15203
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Konstantin Orlov
> Assignee: Konstantin Orlov
> Priority: Major
> Labels: calcite
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Currently the query like follow requires too mush time to optimise (> 5
> minutes on my laptop):
> {code:java}
> select * from t1 inner join t2 on t1.id = t2.id where t1.val1 > 0 or t1.val2
> > 10
> {code}
> 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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
