[
https://issues.apache.org/jira/browse/PHOENIX-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761314#comment-16761314
]
Daniel Wong commented on PHOENIX-374:
-------------------------------------
As discussed offline a bit what is the intended behavior for this with views?
If I made a view of a table with for example a "SELECT * FROM TABLE1 WHERE
val1='TYPE1'", these dynamic columns will be accessable from the child view?
Other views would also inherit these dynamic columns if they were based on a
wild card select as well. Is this the right behavior? Should changes in
sibling views affect each other? Consider another view "SELECT * FROM TABLE1
WHERE val2='POSITION1'" . If I insert a dynamic column into the 1st view it
could show in the second.
> Enable access to dynamic columns in * or cf.* selection
> -------------------------------------------------------
>
> Key: PHOENIX-374
> URL: https://issues.apache.org/jira/browse/PHOENIX-374
> Project: Phoenix
> Issue Type: New Feature
> Reporter: nicolas maillard
> Assignee: Chinmay Kulkarni
> Priority: Critical
> Attachments: PHOENIX-374.patch
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> As of recent work we can now read and write columns that are not in the
> schema, AKA dynamic columns. the Select and Upsert allow dynamic columns to
> be specified.
> I think two additions are still needed.
> - Alter dynamicly: In the Upsert and/or Select statement the ability to add
> on the specified dynamic column to schema. Say Upsert into Table (key,
> cf.dynColumn varchar SCHEMAADD) values (..)
> and for select:
> - select key, cf.dynColumn varchar from T would only read
> - select key from T(cf.dynColumn varchar ) would only read and wrtie to
> schema
> - Select a complete column Family: More complex, accessing a whole Column
> Family with all rows known in schema or not.
> select cf.* from T
> today this works for know columns it could be nice to have this for all
> columns of a family in the schema or not. I'm trying right now to extend this
> to schema for unknown columns. However every new row can a lot of very
> different unknowcolumns. The defined ones will be first but the unknown one
> will be appended at the end.
> This means the metadata might need to be updated at every row to account for
> all new columns discovered.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
