hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aji Janis <aji1...@gmail.com>
Subject Re: When to expand vertically vs. horizontally in Hbase
Date Wed, 03 Jul 2013 13:42:00 GMT
I have a major typo in the question so I apologize. I meant to say 5
families with 1000+ qualifiers each.

Lets work with an example, (not the greatest example here but still). Lets
say we have a Genre Class like this:

Class HistoryBooks{

 ArrayList<Books> author1;
 ArrayList<Books> author2;
 ArrayList<Books> author3;
 ArrayList<Books> author4;
 ArrayList<Books> author5;


Each author is a column family (lets say we only allow 5 authors per
<T>Book class. Book per author ends up being the qualifier. In this case, I
know I have a max family count but my qualifiers have no upper limit. So is
this scenario a case for tall or wide table? Why? Thank you.

On Tue, Jul 2, 2013 at 9:56 AM, Bryan Beaudreault

> If they are accessed mostly together they should all be a single column
> family. The key with tall or wide is based on the total byte size of each
> KeyValue. Your cells would need to be quite large for 50 to become a
> problem. I still would recommend using a single CF though.
> —
> Sent from iPhone
> On Tue, Jul 2, 2013 at 9:33 AM, Aji Janis <aji1705@gmail.com> wrote:
> > The section on Rows vs. Columns at
> > http://hbase.apache.org/book/schema.smackdown.html talks about expanding
> > horizontally vs. vertically.
> > Can someone please explain to me when to choose rows vs. columns. The
> > sections reads, "To be clear, this guideline is in the context is in
> > extremely wide cases, not in the standard use-case where one needs to
> store
> > a few dozen or hundred columns" so if I had 5 column families with 10
> > qualifiers each, accessed mostly together is this a case for wider or
> > taller table? Thanks for any help in advance.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message