Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 23 May 2013 12:00:23 +0000 (UTC)
From: "Liang Xie (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12531831.1321556604011.10154.1369310423156@arcas>
In-Reply-To: <JIRA.12531831.1321556604011@arcas>
References: <JIRA.12531831.1321556604011@arcas>
Subject: [jira] [Updated] (HBASE-4811) Support reverse Scan
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Liang Xie updated HBASE-4811:
-----------------------------

    Attachment: HBase-4811-0.94-v2.txt

a tentative rebase against 0.94 branch(it passed runAllTests in our internal 0.94.3 codebase)
                
> Support reverse Scan
> --------------------
>
>                 Key: HBASE-4811
>                 URL: https://issues.apache.org/jira/browse/HBASE-4811
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client
>    Affects Versions: 0.20.6
>            Reporter: John Carrino
>         Attachments: HBase-4811-0.94.3modified.txt, HBase-4811-0.94-v2.txt
>
>
> All the documentation I find about HBase says that if you want forward and reverse scans you should just build 2 tables and one be ascending and one descending.  Is there a fundamental reason that HBase only supports forward Scan?  It seems like a lot of extra space overhead and coding overhead (to keep them in sync) to support 2 tables.  
> I am assuming this has been discussed before, but I can't find the discussions anywhere about it or why it would be infeasible.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira