Return-Path: X-Original-To: apmail-accumulo-user-archive@www.apache.org Delivered-To: apmail-accumulo-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 62A28EB06 for ; Sat, 16 Feb 2013 01:01:03 +0000 (UTC) Received: (qmail 29306 invoked by uid 500); 16 Feb 2013 01:01:03 -0000 Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org Received: (qmail 29267 invoked by uid 500); 16 Feb 2013 01:01:03 -0000 Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@accumulo.apache.org Delivered-To: mailing list user@accumulo.apache.org Received: (qmail 29257 invoked by uid 99); 16 Feb 2013 01:01:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Feb 2013 01:01:03 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ekohlwey@gmail.com designates 209.85.214.175 as permitted sender) Received: from [209.85.214.175] (HELO mail-ob0-f175.google.com) (209.85.214.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 16 Feb 2013 01:00:55 +0000 Received: by mail-ob0-f175.google.com with SMTP id uz6so4234770obc.34 for ; Fri, 15 Feb 2013 17:00:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=nzyjLzh1MOzQbyaspYg0kWrSE1pVFbrUx2a+X9cAVP4=; b=zmpdfQCGQ9YYBJFBRGCROiwhShT55+HT1sWoy7uKTuW+Z+EN1q82xu3NZfE8NkTWUa u9G0MURaM7q6gdiQOVplU2yXdTvUgf9Opi/hLYChwPMam5fzU+UfkJynglB+qZvjUrt6 0s8Ncbc5nf7kb8HeXBTGKqRsQj4o5IVXv+uEbZQadjvGLt1YSI5tpxAOLbJcimegweIY MSNuZNx7KeMROjLVBPUlPpGJexBiMljY9pkNEQ13cepA/l0s7W7dk10XN03c9lpArskY BLlUhthG26xQLYIBCbvub4VRGm/NVe0D7RFWEQr2iKviah5m/9uLqoOPsB5mBRa/c1A5 39EA== MIME-Version: 1.0 X-Received: by 10.182.220.10 with SMTP id ps10mr3138023obc.21.1360976434909; Fri, 15 Feb 2013 17:00:34 -0800 (PST) Received: by 10.76.74.42 with HTTP; Fri, 15 Feb 2013 17:00:34 -0800 (PST) Received: by 10.76.74.42 with HTTP; Fri, 15 Feb 2013 17:00:34 -0800 (PST) In-Reply-To: <918EAD3D-70E9-43C1-A7C9-E3B63C924D60@cordovas.org> References: <918EAD3D-70E9-43C1-A7C9-E3B63C924D60@cordovas.org> Date: Fri, 15 Feb 2013 20:00:34 -0500 Message-ID: Subject: Re: Reverse timestamp order? From: Ed Kohlwey To: user@accumulo.apache.org Content-Type: multipart/alternative; boundary=f46d044796fdf3530b04d5cd046f X-Virus-Checked: Checked by ClamAV on apache.org --f46d044796fdf3530b04d5cd046f Content-Type: text/plain; charset=ISO-8859-1 On a related note, it would be cool to have the ability to reverse the sorting order completely, basically reading the map files in reverse. There might be some issues with iterator to make data 'look' right but it would be cool to be able to scan back and fourth on tables while generating visualizations, etc. On Feb 15, 2013 7:38 PM, "Aaron Cordova" wrote: > Mike, > > There is no built in way to do this. If you are replaying history more > often than you are grabbing the latest version, you may consider > time-stamping the keys yourself with MAX_LONG - current system time in your > ingest client. > > If you want to grab the whole list and resort, the WholeRowIterator makes > it easy to grab a whole rows worth of data at once, assuming your rows fit > in memory. > > Sent from my iPad > > On Feb 15, 2013, at 6:05 PM, Mike Hugo wrote: > > > When iterating over multiple versions of the same key, is there a way to > receive them in chronological order rather than last inserted first? > > > > For example, if I insert > > > > aKey cf1 cq1 10 aValue1 > > aKey cf1 cq1 20 aValue2 > > aKey cf1 cq1 30 aValue3 > > > > When scanning I receive them in reverse timestamp order - which is great > for retrieving the most recent version > > > > aKey cf1 cq1 30 aValue3 > > aKey cf1 cq1 20 aValue2 > > aKey cf1 cq1 10 aValue1 > > > > If I'd like to "replay" history, should I basically grab the whole list > and then invert it, or is there a built in way to do this? > > > > Thanks! > > > > Mike > > > --f46d044796fdf3530b04d5cd046f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On a related note, it would be cool to have the ability to r= everse the sorting order completely, basically reading the map files in rev= erse. There might be some issues with iterator to make data 'look' = right but it would be cool to be able to scan back and fourth on tables whi= le generating visualizations, etc.

On Feb 15, 2013 7:38 PM, "Aaron Cordova&quo= t; <aaron@cordovas.org> wro= te:
Mike,

There is no built in way to do this. If you are replaying history more ofte= n than you are grabbing the latest version, you may consider time-stamping = the keys yourself with MAX_LONG - current system time in your ingest client= .

If you want to grab the whole list and resort, the WholeRowIterator makes i= t easy to grab a whole rows worth of data at once, assuming your rows fit i= n memory.

Sent from my iPad

On Feb 15, 2013, at 6:05 PM, Mike Hugo <mike@piragua.com> wrote:

> When iterating over multiple versions of the same key, is there a way = to receive them in chronological order rather than last inserted first?
>
> For example, if I insert
>
> aKey cf1 cq1 10 aValue1
> aKey cf1 cq1 20 aValue2
> aKey cf1 cq1 30 aValue3
>
> When scanning I receive them in reverse timestamp order - which is gre= at for retrieving the most recent version
>
> aKey cf1 cq1 30 aValue3
> aKey cf1 cq1 20 aValue2
> aKey cf1 cq1 10 aValue1
>
> If I'd like to "replay" history, should I basically grab= the whole list and then invert it, or is there a built in way to do this?<= br> >
> Thanks!
>
> Mike
>
--f46d044796fdf3530b04d5cd046f--