[
https://issues.apache.org/jira/browse/HBASE-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113034#comment-13113034
]
stack commented on HBASE-4296:
------------------------------
@Jon We want to replace it with something more performant. We don't have the
alternative at the moment. The deprecate was to frighten folks away and have
it so this was then an internal method only. Then in 0.94 we could swap in the
alternative. Can you shim this in your thrift? I suppose you can't if you
want to do the logic for regionserving over in your client that is on the other
side of thrift. And if you are building clients that come to depend on this,
they'll have to be moved to the new method when the new method shows up.
This issue is for 0.92. Will your fat thrift client ship against 0.92 or 0.94?
If 0.92, its there. If 0.94, perhaps hbase-2600 needs to happen sooner rather
than later? (Lars?)
> 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
