there was a schema design talk in HBase conf 2012 (
http://www.slideshare.net/cloudera/5-h-base-schemahbasecon2012). There was
a video but the link from here: http://hbasecon.com/archive.html, but it is
broken
Anyway, if I remember correctly. the idea is to use column(aka
columnfamily) as one layer, and qualifier as another layer, and play some
tricks around it. You may like to take a look to see whether it fits your
needs. The layers has to be simple, or an alternative is to save a json
file(or other structured file format as the raw value)
Demai
On Mon, Sep 8, 2014 at 2:06 PM, Stephen Boesch <java...@gmail.com> wrote:
> While I am aware that HBase does not have native support for nested
> structures, surely there are some of you that have thought through this use
> case carefully.
>
> Our particular use case is likely having single digit nested layers with
> tens to hundreds of items in the lists at each level.
>
> An example would be a
>
> top Level 300 items
> middle level : 1 to 100 items ("1 value" may indicate a single value as
> opposed to a list)
> third level: 1 to 50 items
> fourth level 1 to 20 items
>
> The column names are likely known ahead of time- which may or may not
> matter for hbase. We could model the above structure in a Parquet File or
> in Hive (with nested struct's)- but we would like to consider whether
> HBase.might also be an option.
>
