Hi Usman
I am going through the same thing.
Unless you have a reason to use wide rows (e.g. you need atomic
updates on multiple points within one row) I recommend using a tall
table, since large rows will become unmanageable, especially if they
keep growing forever (and HBase cannot
I want to do this so i can use the timestamp attribute for a cell as a
search criteria over my data which is inside a daily table.
The daily table starts from lets say Jan 1st 2010 onwards and I plan to
have 10 column families. So i have to populate for past dates with the
prior daily
On Wed, Mar 2, 2011 at 12:22 AM, Usman Waheed usm...@opera.com wrote:
I want to do this so i can use the timestamp attribute for a cell as a
search criteria over my data which is inside a daily table.
Reminder: the timestamp should be in milliseconds. If you store a
timestamp in seconds, I'm
Hi,
Please see my comments inline and Thanks for the tips.
They were very helpful in getting a better understanding of Hbase and
schema design.
Regards,
Usman
On Wed, Mar 2, 2011 at 12:22 AM, Usman Waheed usm...@opera.com wrote:
I want to do this so i can use the timestamp attribute for a
Why do you need to specify the timestamp? Why not let the server do it?
Otherwise, the below should work for all but the case where many
clients writing from different machines with unsync'd clocks.
St.Ack
On Tue, Mar 1, 2011 at 3:18 PM, Usman Waheed usm...@opera.com wrote:
Hi,
I have a
