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

Gabriel Reid resolved PHOENIX-319.
----------------------------------

    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.

> DynamicColumns next steps
> -------------------------
>
>                 Key: PHOENIX-319
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-319
>             Project: Phoenix
>          Issue Type: Task
>            Reporter: maillard
>
> Hi everyone
> The issues -9 and -125 aka dynamic column and family querying give a test of 
> a little of the nosql feature of hbase but, for my use case,  I am still 
> lacking a bit of power.
> Basically I often use hbase as a key value store for keys and values I do not
> know and the family will hold the logic of what it is. Like a list of user 
> ids and how much they spent. I know the LIST family will hold all these 
> values and I can query all of them or some of them. In this situation the 
> table schema can't have a defined column since the keys will move around a 
> lot.
> For this use case you need to be able to write and read on the fly with 
> little or no notion of schema. 
> Kinda like mariadb with it's dynamic columns feature.
> "INSERT INTO tbl SET dyncol_blob=COLUMN_CREATE("column_name", "value");"
> "COLUMN_LIST(dyncol_blob);"
> https://kb.askmonty.org/en/dynamic-columns/_column_list
> Event more importantly the possibility to read from that family without 
> knowing the name of the column just knowing you want all or some.
> Does this seem like something phoenix wants to support.
> I was looking at the source code to see where this could be done, and I'm 
> struck after the phoenixstatement execute, I see where the scan is created 
> and where the columns are projected, I just can't see where this is sent to 
> the coprocessors and where it answers back.
>  if this is something of interest I'm more than willing to work on it as this 
> is a use or no use of phoenix in my company.
> thanks for all the hard work



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

Reply via email to