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/06/10 00:29:01 UTC

[jira] [Resolved] (CALCITE-749) Use a Factory in MaterializationService to create tables

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

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

Fixed in http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/8b53dc49.

Thanks, Rajat!

> Use a Factory in MaterializationService to create tables
> --------------------------------------------------------
>
>                 Key: CALCITE-749
>                 URL: https://issues.apache.org/jira/browse/CALCITE-749
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: Rajat Venkatesh
>            Assignee: Julian Hyde
>             Fix For: 1.4.0-incubating
>
>
> Follow up of this [conversation|https://mail-archives.apache.org/mod_mbox/incubator-calcite-dev/201503.mbox/%3CCANG6QPx7eLmUrkXRTY09yGw7GchMNRSSDnRCQEnd_3z%3DJCX%3Dgg%40mail.gmail.com%3E]
> There are two tasks:
> 1. Use a Factory to create tables that represent a materialized view.
> 2. Add an entry to the schema only if a materialized table was created in defineMaterialization.
> I'll open a WIP progress soon. 
> 1. was easy to implement.
> 2. is proving to be hard because rest of the code requires a CalciteSchema.TableEntry object which is available only when a table is added to schema. I dont know how to get an object for an existing entry.  



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