Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of sonalgoyal4@gmail.com
 designates 209.85.220.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1313818002.8846.YahooMailNeo@web121702.mail.ne1.yahoo.com>
References: <4E4F104C.3070400@gmail.com>
	<1313818002.8846.YahooMailNeo@web121702.mail.ne1.yahoo.com>
Date: Sat, 20 Aug 2011 15:21:20 +0530
Message-ID: 
 <CAKTawbJnxbOumjVk4awq1LnRYh-Tk1BDzBROuYUQ-ZszzzgGxw@mail.gmail.com>
Subject: Re: Reverse timestamp
From: Sonal Goyal <sonalgoyal4@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=bcaec5016467bd1af904aaecc9cf

--bcaec5016467bd1af904aaecc9cf
Content-Type: text/plain; charset=ISO-8859-1

Hi Mark,

Here is an example for generating reverse timestamps. Hope it helps:

http://devblog.streamy.com/2009/04/23/hbase-row-key-design-for-paging-limit-offset-queries/

Best Regards,
Sonal
Crux: Reporting for HBase <https://github.com/sonalgoyal/crux>
Nube Technologies <http://www.nubetech.co>

<http://in.linkedin.com/in/sonalgoyal>


On Sat, Aug 20, 2011 at 10:56 AM, lars hofhansl <lhofhansl@yahoo.com> wrote:

> HBase maps (row-key, column family name, column, timestamp) to a value.
>
> The KeyValues are also sorted by the same attributes in reverse timestamp
> order.
>
> The default timestamp is the current time, but you can set any long value
> (which does not need correlate in any way to the time domain)
> as the time stamp and hence define your own ordering within multiple
> version of the same row key.
>
> See Put: Put(byte[] row, long ts).
>
> Is that what you meant?
>
> -- Lars
>
>
>
> ________________________________
> From: Mark <static.void.dev@gmail.com>
> To: user@hbase.apache.org
> Sent: Friday, August 19, 2011 6:39 PM
> Subject: Reverse timestamp
>
> I understand the need but I don't understand how to generate a reverse
> timestamp. Can someone please explain how this is accomplished and how I can
> test that its working correctly?
>
> Thanks
>

--bcaec5016467bd1af904aaecc9cf--