[jira] [Resolved] (CALCITE-493) Add EXTEND clause, for defining columns and their types at query/DML time

["Julian Hyde (JIRA)" <ji...@apache.org>]

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

Julian Hyde resolved CALCITE-493.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0-incubating

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

Rather than adding a method to {{Table}}, I created a new {{interface ExtensibleTable extends Table}} with a method {{Table extend(List<RelDataTypeField>)}}. If an adapter supports extensions for hidden columns, then you should make your {{Table}} objects implement {{ExtensibleTable}}.

> Add EXTEND clause, for defining columns and their types at query/DML time
> -------------------------------------------------------------------------
>
>                 Key: CALCITE-493
>                 URL: https://issues.apache.org/jira/browse/CALCITE-493
>             Project: Calcite
>          Issue Type: Improvement
>            Reporter: James Taylor
>            Assignee: Julian Hyde
>              Labels: phoenix
>             Fix For: 1.0.0-incubating
>
>
> Often times only being able to define a static schema over which to query is not flexible enough. It would be useful to be able to define columns and their type at query/DML time. For an example syntax, see http://phoenix.apache.org/dynamic_columns.html



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