You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Kevin Liew (JIRA)" <ji...@apache.org> on 2017/03/14 04:14:41 UTC

[jira] [Comment Edited] (CALCITE-504) Support adding new columns when creating/altering VIEW

    [ https://issues.apache.org/jira/browse/CALCITE-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923526#comment-15923526 ] 

Kevin Liew edited comment on CALCITE-504 at 3/14/17 4:13 AM:
-------------------------------------------------------------

This is implemented as part of CALCITE-1666

We initialize a mock table for testing in {{MockCatalogReader}} defined by:
{code:sql}
"select ENAME, EMPNO, JOB, DEPTNO, SLACKER, SAL, EXTRA, HIREDATE, MGR, COMM"
            + " from EMPDEFAULTS extend (EXTRA boolean)"
            + " where DEPTNO = 20"
{code}


was (Author: kliew):
This is implemented as part of CALCITE-1666

We initialize a mock table for testing in {{MockCatalogReader}}:
{code:sql}
"select ENAME, EMPNO, JOB, DEPTNO, SLACKER, SAL, EXTRA, HIREDATE, MGR, COMM"
            + " from EMPDEFAULTS extend (EXTRA boolean)"
            + " where DEPTNO = 20"
{code}

> Support adding new columns when creating/altering VIEW
> ------------------------------------------------------
>
>                 Key: CALCITE-504
>                 URL: https://issues.apache.org/jira/browse/CALCITE-504
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: James Taylor
>            Assignee: Julian Hyde
>              Labels: phoenix
>
> When the underlying storage layer allows more flexibility in defining a schema, it's useful to allow a VIEW to define new columns. It'd be great if Calcite supported this as well. See http://phoenix.apache.org/views.html and http://phoenix.apache.org/multi-tenancy.html for examples.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)