[
https://issues.apache.org/jira/browse/HBASE-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113037#comment-13113037
]
Jonathan Gray commented on HBASE-4296:
--------------------------------------
We are already using the fat thrift client on our 0.90 branch. I'm in the
process of pushing this all out into open source so we can then pull it back in
to our 0.92 based branch. I'm happy to put this stuff into 0.92 in Apache as
well but it's somewhat featurish :)
Was the method removed in 0.94 already? Can we just hold off on removing it
into 2600 happens and that way it won't matter and we can commit it anywhere.
Following 2600 we can modify how it works and just use a normal scanner then?
> Deprecate HTable[Interface].getRowOrBefore(...)
> -----------------------------------------------
>
> Key: HBASE-4296
> URL: https://issues.apache.org/jira/browse/HBASE-4296
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.92.0
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Trivial
> Fix For: 0.92.0
>
> Attachments: 4296.txt
>
>
> HTable's getRowOrBefore(...) internally calls into Store.getRowKeyAtOrBefore.
> That method was created to allow our scanning of .META. (see HBASE-2600).
> Store.getRowKeyAtOrBefore(...) lists a bunch of requirements for this to be
> performant that a user of HTable will not be aware of.
> I propose deprecating this in the public interface in 0.92 and removing it
> from the public interface in 0.94. If we don't get to HBASE-2600 in 0.94 it
> will still remain as internal interface for scanning meta.
> Comments?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
