[
https://issues.apache.org/jira/browse/CALCITE-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Haisheng Yuan updated CALCITE-3927:
-----------------------------------
Description:
In VolcanoPlanner, when set gets merged, planner fires rules again for RelNodes
in both sets, but not for RelSubset. We might miss something because of this.
If all the logical transformation rules and physical implementation rules are
separated out in different stage and physical rules don't do logical work, we
might be OK. But the reality is that all the things are mixed together at the
moment.
was:
In VolcanoPlanner, when set gets merged, planner fires rules again for RelNodes
in both sets, but not for RelSubset. We might miss something because of this.
If all the logical transformation rules and physical implementation rules are
separated out and physical rules don't do logical work, we might be OK. But the
reality is that all the things are mixed together at the moment.
> RelSubset is not fired for rule when set gets merged
> ----------------------------------------------------
>
> Key: CALCITE-3927
> URL: https://issues.apache.org/jira/browse/CALCITE-3927
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Haisheng Yuan
> Priority: Major
>
> In VolcanoPlanner, when set gets merged, planner fires rules again for
> RelNodes in both sets, but not for RelSubset. We might miss something because
> of this.
> If all the logical transformation rules and physical implementation rules are
> separated out in different stage and physical rules don't do logical work, we
> might be OK. But the reality is that all the things are mixed together at the
> moment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
