[
https://issues.apache.org/jira/browse/PHOENIX-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Reid resolved PHOENIX-140.
----------------------------------
Resolution: Fixed
Bulk resolve of closed issues imported from GitHub. This status was reached by
first re-opening all closed imported issues and then resolving them in bulk.
> Allow columns to be defined at query time
> -----------------------------------------
>
> Key: PHOENIX-140
> URL: https://issues.apache.org/jira/browse/PHOENIX-140
> Project: Phoenix
> Issue Type: Task
> Reporter: James Taylor
> Labels: enhancement
>
> Sometimes defining a schema up front is not feasible. Instead, a subset of
> columns may be specified up front when creating the table while the rest
> would be specified at query time. One way of specifying this could be to
> define the columns in parens after the table in the FROM clause like this:
> SELECT col1,col2,col3 FROM my_table(col2 VARCHAR, col3 INTEGER) WHERE col3 >
> 10
> From an implementation point of view, this would not be too hard to do.
> Phoenix caches metadata for a table on the client-side through the PTable
> interface. We could create a new implementation associated with the statement
> context that delegates to the statically defined one, but allows new columns
> to be added.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
