[
https://issues.apache.org/jira/browse/CALCITE-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176726#comment-17176726
]
Haisheng Yuan commented on CALCITE-3916:
----------------------------------------
Thanks for your detailed explanation., [~rubenql]!
We need to investigate the root cause of the regression for your pattern, I can
imagine it might hard to create a repro test case, but if you can, that would
be great.
Usually the operator(IndexScan45) generated from "passThrough" should better
have the same convention with original operator (IndexScan38), ignore the
required "ENUMERABLE" convention, have you tried that?
> Support cascades style top-down driven rule apply
> -------------------------------------------------
>
> Key: CALCITE-3916
> URL: https://issues.apache.org/jira/browse/CALCITE-3916
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Haisheng Yuan
> Assignee: Jinpeng Wu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.24.0
>
> Time Spent: 15.5h
> Remaining Estimate: 0h
>
> Apply rules by leaf RelSet -> root RelSet order. For every RelNode in a
> RelSet, rule is matched and applied sequentially. No RuleQueue and
> DeferringRuleCall is needed anymore. This will make space pruning and rule
> mutual exclusivity check possible.
> Rule that use AbstractConverter as operand is an exception, to keep backward
> compatibility, this kind of rule still needs top-down apply.
> This should be done after CALCITE-3896.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
