You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2021/07/28 15:49:00 UTC

[jira] [Commented] (IGNITE-15203) Calcite. Extract Filter and Project related rules to separate HEP phase

    [ https://issues.apache.org/jira/browse/IGNITE-15203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17388859#comment-17388859 ] 

Konstantin Orlov commented on IGNITE-15203:
-------------------------------------------

[~alexpl], [~zstan], folks, do a review please

> 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
>          Time Spent: 10m
>  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)