Critical Description
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.
Attachments
Attachments
Issue Links
- relates to
-
PHOENIX-5129 Evaluate using same cell as the data cell for storing dynamic column metadata
-
- Open
-
- links to
