You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2017/05/16 10:38:04 UTC
[jira] [Commented] (CALCITE-1791) Support view partial rewriting in
join materialized view rewriting
[ https://issues.apache.org/jira/browse/CALCITE-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012121#comment-16012121 ]
Jesus Camacho Rodriguez commented on CALCITE-1791:
--------------------------------------------------
Fixed in http://git-wip-us.apache.org/repos/asf/calcite/commit/6689c75.
> Support view partial rewriting in join materialized view rewriting
> ------------------------------------------------------------------
>
> Key: CALCITE-1791
> URL: https://issues.apache.org/jira/browse/CALCITE-1791
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Fix For: 1.13.0
>
>
> Simple extension for {{AbstractMaterializedViewRule}} to support case when view contains a subset of the tables of the query and tables are joined in different order in the query and view plans.
> For instance:
> View (m0): {{(A JOIN B) JOIN C}}
> Query: {{(((A JOIN B) JOIN D) JOIN C) JOIN E}}
> MV rewriting: {{((m0 JOIN D) JOIN E)}}
> Basically, once we have found the missing tables, we add them to the view and view plan. Then the rewriting algorithm works the same way and will enforce any predicate that is in the query and not in the view.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)