[
https://issues.apache.org/jira/browse/HBASE-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678933#comment-13678933
]
Lars Hofhansl commented on HBASE-4811:
--------------------------------------
The idea is great, I love that feature. It was long deemed impossible to do
this at all.
But the patch can be improved. Can we at least get rid of the class casts?
-0 from me for the current form. (I'm not going to block it)
Maybe somebody else should have a look too ([[email protected]], [~sershe],
[[email protected]], [[email protected]])?
I will have some time after HBaseCon, so I can have a try at improving the
patch (and as I said the general architecture is sound).
> 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, 0.94.7
> Reporter: John Carrino
> Assignee: Liang Xie
> Attachments: 4811-trunk-v5.patch, HBase-4811-0.94.3modified.txt,
> HBase-4811-0.94-v2.txt, hbase-4811-trunkv1.patch, hbase-4811-trunkv4.patch,
> hbase-4811-trunkv6.patch, hbase-4811-trunkv7.patch
>
>
> 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
