[
https://issues.apache.org/jira/browse/CALCITE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14247526#comment-14247526
]
Julian Hyde commented on CALCITE-493:
-------------------------------------
Not at present. It could be extended to handle table functions, if there's a
need for it. The hardest part would be extending the TableFunction interface to
ask for the extra columns (analogous to how we added ExtensibleTable extends
Table). I'd like to see a real use case before I jump in and do it.
By the way, TableMacro could be made extensible too, and with less effort than
TableFunction; its apply method would just need to return a TranslatableTable
that also implements 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: Sub-task
> 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)
