You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by "Haisheng Yuan (Jira)" <ji...@apache.org> on 2020/01/21 23:12:00 UTC

[jira] [Created] (CALCITE-3753) Always try to match and execute substitution rule first and remove rulematch ordering

Haisheng Yuan created CALCITE-3753:
--------------------------------------

             Summary: Always try to match and execute substitution rule first and remove rulematch ordering
                 Key: CALCITE-3753
                 URL: https://issues.apache.org/jira/browse/CALCITE-3753
             Project: Calcite
          Issue Type: Improvement
          Components: core
            Reporter: Haisheng Yuan


Some rules e.g. ProjectMergeRule, PruneEmptyRule can be defined as SubstitutionRule, so that we can always try to match and execute them first (without deferring rule call). All the other rulematches doesn't need to be sorted and rules can be executed in any order they matched, since we are going to execute all of them anyway, sooner or later. Computing and comparing importances cause a lot of latency.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)