[
https://issues.apache.org/jira/browse/PHOENIX-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165796#comment-14165796
]
Jonathan Leech commented on PHOENIX-150:
----------------------------------------
It would be equally valuable to be able to define secondary indexes in this
nested fashion; e.g. a single hybrid secondary index across multiple tables to
answer the join efficiently.
The above + function based indexes would enable interesting data warehousing /
BI. I just watched Josh Willis' presentation on what he called "supernova
schemas" and this could enable that within Phoenix defined all in SQL.
Also could do some interesting things with hooks into replication in addition
to / instead of coprocessors.
> Support nested child rows
> -------------------------
>
> Key: PHOENIX-150
> URL: https://issues.apache.org/jira/browse/PHOENIX-150
> Project: Phoenix
> Issue Type: Task
> Reporter: James Taylor
> Assignee: Anoop Sam John
> Labels: enhancement
>
> Unlike with standard relational databases, HBase allows you the flexibility
> of dynamically creating as many key values in a row as you'd like. Phoenix
> could leverage this by providing a way to model child rows inside of a parent
> row. The child row would be comprised of the set of key values whose column
> qualifier is prefixed with a known name and appended with the primary key of
> the child row. Phoenix could hide all this complexity, and allow querying
> over the nested children through joining to the parent row.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
