[
https://issues.apache.org/jira/browse/CALCITE-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142947#comment-16142947
]
Maryann Xue commented on CALCITE-1966:
--------------------------------------
I think using qualified name instead of RelOptTable in RelOptMaterialization is
fine, since the original reference to the RelOptTable is no more than getting
the table's name and replacing it has no other impact. I have a couple of other
minor suggestions in the PR, though.
> Support for normal views to act as materialization table
> --------------------------------------------------------
>
> Key: CALCITE-1966
> URL: https://issues.apache.org/jira/browse/CALCITE-1966
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Christian Beikov
> Assignee: Julian Hyde
>
> Currently, it seems a materialized view can only have it's materialization in
> a real table, although it might be nice to be able to use a view instead.
> Since external data stores like e.g. elasticsearch aren't might have
> different data representations, the mismatch has to be overcome by doing
> casts in a view.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
