[
https://issues.apache.org/jira/browse/IGNITE-15203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392063#comment-17392063
]
Evgeny Stanilovsky commented on IGNITE-15203:
---------------------------------------------
after this pr will be merged [1] will be fixed, [~korlov] may be you append
additional test ? It`s ok on your branch and burns cpu on mainstream.
{noformat}
assertQuery(client, "SELECT salary FROM account WHERE salary < ALL (
SELECT 1 )")
.check();
{noformat}
[1] https://issues.apache.org/jira/browse/IGNITE-14721
> 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: calcite2-required, calcite3-required
> Time Spent: 1h 50m
> 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.3.4#803005)
