[
https://issues.apache.org/jira/browse/HBASE-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13155573#comment-13155573
]
stack commented on HBASE-4811:
------------------------------
I'd suggest you spend more time w/ the code base to see how much of effort
would be required doing a reverse scan (Superficially, yes, our MemStore is a
NavigableSet but that is not what client interacts with; ditto our sstable-like
hfile thing. IIRC leveldb counsels that the reverse range is going against the
grain and at a minimum is much slower than the natural scan).
> 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
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
