https://community.cloudera.com/t5/Support-Questions/Hbase-tall-narrow-or-flat-wide-design/m-p/158097#M120496 <P>Hello arunkumar</P><P>As a general rule it will come back to what you are trying to achieve and how you want to service data. Remember that Hbase's performance is directly derived from the rowkey and hence how you access data. Hbase will split up data in regions served by region servers and on a lower level data will be split by Column Family. A single entry however will be served by the same region. At high level the difference between tall-narrow and flat-wide comes back to scans vs gets. Since Hbase has an ordered on the rowkey storage policy and full scans are costly. A Tall-narrow approach would be to have a more complex rowkey giving adjacency of similar elements and allowing to do focused scans for logical group of entries. A Flat-wide approach would ahve much more information in the entry itself, you "get" the entry through the rowkey and the entry would have sufficient information to do your compute or answer your query.</P><P>hope this helps</P> Wed, 06 Apr 2016 14:05:27 GMT nmaillard1 2016-04-06T14:05:27Z https://community.cloudera.com/t5/Support-Questions/Hbase-tall-narrow-or-flat-wide-design/m-p/158096#M120495 <P>Can anyone throw some light on the hbase table design. which one should one use "tall-narrow or flat wide design" and for which use case.</P> Wed, 06 Apr 2016 13:07:18 GMT https://community.cloudera.com/t5/Support-Questions/Hbase-tall-narrow-or-flat-wide-design/m-p/158096#M120495 arunpoy 2016-04-06T13:07:18Z https://community.cloudera.com/t5/Support-Questions/Hbase-tall-narrow-or-flat-wide-design/m-p/158097#M120496 <P>Hello arunkumar</P><P>As a general rule it will come back to what you are trying to achieve and how you want to service data. Remember that Hbase's performance is directly derived from the rowkey and hence how you access data. Hbase will split up data in regions served by region servers and on a lower level data will be split by Column Family. A single entry however will be served by the same region. At high level the difference between tall-narrow and flat-wide comes back to scans vs gets. Since Hbase has an ordered on the rowkey storage policy and full scans are costly. A Tall-narrow approach would be to have a more complex rowkey giving adjacency of similar elements and allowing to do focused scans for logical group of entries. A Flat-wide approach would ahve much more information in the entry itself, you "get" the entry through the rowkey and the entry would have sufficient information to do your compute or answer your query.</P><P>hope this helps</P> Wed, 06 Apr 2016 14:05:27 GMT https://community.cloudera.com/t5/Support-Questions/Hbase-tall-narrow-or-flat-wide-design/m-p/158097#M120496 nmaillard1 2016-04-06T14:05:27Z