hadoop-common-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From edward choi <mp2...@gmail.com>
Subject Why use "Reverse Timestamp" as the Row Key?
Date Fri, 22 Jul 2011 07:18:29 GMT
I was studying Hbase with "Hadoop: The Definitive Guide".
There was a schema example that had as the row key, "Group Id + Reverse
This way the same groups will be located near one another in the table.
Plus, within the same group, rows will be sorted so that the most recently
inserted row will be located at the first.

The part I don't understand is, what is the advantage of using "Reverse
Timestamp" instead of just "Timestamp"?
Why place the newest row on the top?
I thought in Hbase, keys are searched by binary search. And in binary
search, the chronological order has no effect (at least that's how I
understand it).
So why put an extra step to reverse the timestamp?

Any explanation will be much appreciated.


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