[
https://issues.apache.org/jira/browse/CALCITE-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jin xing updated CALCITE-3273:
------------------------------
Description:
In current implementation of rules in SubstitutionVisitor.java &
MaterializedViewSubstitutionVisitor.java, it's quite common to add a
compensating Project on top of child node of target(MV-rel) during matching.
But afterwards the next round matching should be able to handle such a
compensated Project and match upward along the plan tree. Otherwise we fail the
matching. After all, the goal of matching is to transform the query and let a
complete 'target' show up in the transformed query plan.
I opened this as a parent JIRA to add MV matching rules that consider
compensating MutableProject.
> Materialization matching rules that consider compensating MutableProject
> ------------------------------------------------------------------------
>
> Key: CALCITE-3273
> URL: https://issues.apache.org/jira/browse/CALCITE-3273
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: jin xing
> Priority: Major
>
> In current implementation of rules in SubstitutionVisitor.java &
> MaterializedViewSubstitutionVisitor.java, it's quite common to add a
> compensating Project on top of child node of target(MV-rel) during matching.
> But afterwards the next round matching should be able to handle such a
> compensated Project and match upward along the plan tree. Otherwise we fail
> the matching. After all, the goal of matching is to transform the query and
> let a complete 'target' show up in the transformed query plan.
> I opened this as a parent JIRA to add MV matching rules that consider
> compensating MutableProject.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
