Hi Genady!
If everything goes as planned there will be a possibility to input a
TimeRange into every get query in 0.20, so that you will
be able to do the call, give me all data from row r, family f and column c
in the timerange t2 to t1. The nice thing about the
new implementation is also that you
late.com]
> > Sent: Friday, April 03, 2009 2:56 AM
> > To: hbase-user@hadoop.apache.org
> > Subject: RE: timestamp uses
> >
> > Jonathan,
> >
> > Please correct me If I wrong, but one of the features that HBase
> obviously
> > missing is possibility
: hbase-user@hadoop.apache.org
> Subject: RE: timestamp uses
>
> Jonathan,
>
> Please correct me If I wrong, but one of the features that HBase obviously
> missing is possibility to select records based on timestamp range(week,
> month, etc.), as far as understand, it's po
anges. To
solve it there is always option to put time/date as row key, but in most
designs you can't do it.
Thanks,
Gennady
-Original Message-
From: Jonathan Gray [mailto:jl...@streamy.com]
Sent: Wednesday, April 01, 2009 7:55 PM
To: hbase-user@hadoop.apache.org
Subject: RE: timestamp
, I've found that it makes more sense to encode stamps in
your row keys or column names.
Hope that helps.
JG
> -Original Message-
> From: Wes Chow [mailto:wes.c...@s7labs.com]
> Sent: Wednesday, April 01, 2009 5:56 AM
> To: hbase-user@hadoop.apache.org
> Subject: timestamp
So far, few if any of the schema designs I've come across have really
talked about using the timestamp field and HBase's automatic deletion of
old cells in a smart way.
What is the timestamp typically used for? Snapshotting? Implementing
more complicated transactions than HBase natively supp
