You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/07/17 02:13:04 UTC

[jira] [Resolved] (CALCITE-787) Star table wrongly assigned to materialized view

     [ https://issues.apache.org/jira/browse/CALCITE-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-787.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.4.0-incubating

Fixed in http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/d38e6b1b. Thanks for the patch!

> Star table wrongly assigned to materialized view
> ------------------------------------------------
>
>                 Key: CALCITE-787
>                 URL: https://issues.apache.org/jira/browse/CALCITE-787
>             Project: Calcite
>          Issue Type: Task
>          Components: core
>    Affects Versions: 1.3.0-incubating, 1.4.0-incubating
>            Reporter: Amogh Margoor
>            Assignee: Julian Hyde
>             Fix For: 1.4.0-incubating
>
>
> cc: [~vrajat]
> CalciteMaterializer tries to rewrite query relnode with the star table in schema (the first one that fits). Utility function used is RelOptMaterialization::tryUseStar. Utility function should return null when it cannot rewrite relnode using star table, but instead it is returning the same relnode back. This is causing MV being assigned star table even when it is not required. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)