Date: Tue, Oct 16, 2012 at 2:53 PM
Subject: crafting your key - scan vs. get
To: user@hbase.apache.orgmailto:user@hbase.apache.org
Hopefully this is a fun question. :)
Assume you could architect an HBase table from scratch and you were
choosing between the following two key structures
Neil,
I've pointed you in the right direction.
The rest of the exercise is left to the student. :-)
While you used the comment about having fun, your question is boring. *^1
The fun part is for you now to play and see why I may have suggested the
importance of column order.
Sorry, but that
...@gmail.commailto:neilyalow...@gmail.com
Date: Tue, Oct 16, 2012 at 2:53 PM
Subject: crafting your key - scan vs. get
To: user@hbase.apache.orgmailto:user@hbase.apache.org
Hopefully this is a fun question. :)
Assume you could architect an HBase table from scratch and you were
choosing between the following two
Neil,
Since you asked
Actually your question is kind of a boring question. ;-) [Note I will probably
get flamed for saying it, even if it is the truth!]
Having said that...
Boring as it is, its an important topic that many still seem to trivialize in
terms of its impact on performance.
This is a helpful response, thanks. Our use case fits the Show me the
most recent events by user A you described.
So using the first example, a table populated with events of user ID AA.
ROWCOLUMN+CELL
AA
column=data:event,
Hopefully this is a fun question. :)
Assume you could architect an HBase table from scratch and you were
choosing between the following two key structures.
1)
The first structure creates a unique row key for each PUT. The rows are
events related to a user ID. There may be up to several
