Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 5 Mar 2015 22:59:38 +0000 (UTC)
From: "Josh Elser (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12779890.1425588752000.15683.1425596378305@Atlassian.JIRA>
In-Reply-To: <JIRA.12779890.1425588752000@Atlassian.JIRA>
References: <JIRA.12779890.1425588752000@Atlassian.JIRA>
 <JIRA.12779890.1425588752920@arcas>
Subject: [jira] [Updated] (ACCUMULO-3648) Ability to Scan Table Keys in
 Reverse Order
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-3648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser updated ACCUMULO-3648:
---------------------------------
    Issue Type: New Feature  (was: Improvement)

> Ability to Scan Table Keys in Reverse Order
> -------------------------------------------
>
>                 Key: ACCUMULO-3648
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3648
>             Project: Accumulo
>          Issue Type: New Feature
>          Components: master, tserver
>            Reporter: Mike Fagan
>            Priority: Minor
>              Labels: features, performance
>
> There are cases where you would like to scan a table in reverse key order.
> For example: 
> Consider a table using an inverted timestamp key.
> This allows for very quick access to the latest records.
> But  It would be helpful to quickly access earliest records without having to:
> A) scan through all the records to build a collection to reverse sort
> B) store the table again using the reverse key


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)