You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Amogh Margoor (JIRA)" <ji...@apache.org> on 2015/07/06 14:50:04 UTC
[jira] [Commented] (CALCITE-787) Star table is being assigned to
MaterializedView even when it's not required.
[ https://issues.apache.org/jira/browse/CALCITE-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614987#comment-14614987 ]
Amogh Margoor commented on CALCITE-787:
---------------------------------------
Hi [~julianhyde]
PR is raised for this which contains fix and the reproducer: https://github.com/apache/incubator-calcite/pull/103
Please take a look.
Regards,
Amogh
> Star table is being assigned to MaterializedView even when it's not required.
> -----------------------------------------------------------------------------
>
> 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
>
> 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)