[ https://issues.apache.org/jira/browse/CALCITE-3916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17157108#comment-17157108 ]
Haisheng Yuan commented on CALCITE-3916: ---------------------------------------- Yes, doing the final round review > 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: 12h 40m > 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)