[jira] [Resolved] (PHOENIX-354) Dynamic Writes

["Gabriel Reid (JIRA)" <ji...@apache.org>]

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

Gabriel Reid resolved PHOENIX-354.
----------------------------------

    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.

> Dynamic Writes
> --------------
>
>                 Key: PHOENIX-354
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-354
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: maillard
>
> This would the write part of the Dynamic Columns -9
> Sometimes defining a static schema up front is not feasible. Instead, a subset of columns may be specified at table create time while the rest would be specified at write time.
> As James pointed out it could look like this:
> UPSERT INTO t (pk, col1, col2, dynCol3 VARCHAR) VALUES (?, ?, ?, ?);
> The upsert would need to check the table schema and check the colum family exists and the column qualifier does'nt. If it does maybe just gracefully write as if had been correctly entered. If unknown and valid the table schema would need to be updated.
> A concerning secondary issue might be when writing very large column families to hold a bunch of values, say a list of userids that did something. In such a case would we offer a way to not update to table schema and this list would be later queried as whole Family?



--
This message was sent by Atlassian JIRA
(v6.2#6252)