[
https://issues.apache.org/jira/browse/IGNITE-18688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17719794#comment-17719794
]
Andrey Mashenkov commented on IGNITE-18688:
-------------------------------------------
Just check how the test passed before IGNITE-18213.
After planner processed all tree nodes from the top to the bottom, it found
TableScan's traits mismatch and tried to propagate rewindability trait from the
bottom to the top. Propagating rewindability traits creates TableSpool nodes in
each rel-set at the bottom-up path.
Every newly created TableSpool forced planner to optimize rel-sets once again
as for physical nodes (table spools) as for logical nodes.
Optimization for logical nodes caused ProjectableFilterableTableScan pulling
from child levels. Thankfully to the trait propagation process, which queue
nodes for re-planning in the 'right' order, re-optimization was done in
bottom-up manner. Thus, ProjectableFilterableTableScan was pulled up as much
higher as possible.
As of now, there is no rewindability traits and this trick can't be exploited
anymore. Also, there is no access to TopDownRuleDriver and no other way to hint
the TopDownRuleDriver that some node or relset need one more optimization try.
> Sql. Filter and Project are not merged to TableScan
> ---------------------------------------------------
>
> Key: IGNITE-18688
> URL: https://issues.apache.org/jira/browse/IGNITE-18688
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Konstantin Orlov
> Assignee: Andrey Mashenkov
> Priority: Major
> Labels: ignite-3
>
> After IGNITE-18213 the test
> {{org.apache.ignite.internal.sql.engine.planner.ProjectFilterScanMergePlannerTest#testFilterProjectFilterMerge}}
> start to fail. Need to investigate and fix the problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
