[
https://issues.apache.org/jira/browse/CALCITE-1966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16140498#comment-16140498
]
Julian Hyde commented on CALCITE-1966:
--------------------------------------
I reviewed
https://github.com/apache/calcite/pull/527/commits/dbc70ef36e7364509f2ee6586515c266cbf4077a,
and it looks good, except that we need a test.
[~maryannxue] can you also review? I want to make sure that dropping
RelOptTable doesn't remove options later on: I don't remember whether a
RelOptTable can always be re-created from its fully-qualified name.
> 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)
