[
https://issues.apache.org/jira/browse/PHOENIX-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Reid resolved PHOENIX-370.
----------------------------------
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.
> Support complex data types
> --------------------------
>
> Key: PHOENIX-370
> URL: https://issues.apache.org/jira/browse/PHOENIX-370
> Project: Phoenix
> Issue Type: Task
> Reporter: maillard
>
> One of the, many, key advantages of hbase is to give you freedom in what and
> how you store and phoenix gives you method. In the same way hive and impala
> (soon) offer more complex data structures we could offer in phoenx types like:
> Arrays
> Maps
> and json,xml even html
> the former would be kind of like the keys a list of values separated by a
> zero byte.
> The maps could be a specific column famliy or a set of key:values with the
> keys having a specific naming convention.
> The later xml,json,html could just be strings accessed and parsed if needed
> with, xpath,jsopnpath and jsoup (css query)
> Does anyone else have such needs or use cases?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
