[
https://issues.apache.org/jira/browse/HBASE-4296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13113676#comment-13113676
]
stack commented on HBASE-4296:
------------------------------
We can hold off till 2600 is done.
I don't think we can call it scanMeta or do you mean scanMetaGetRowOrBefore?
The latter we could do.
I'd think that when 2600 goes in, this method just won't make sense any more --
clients that find regions using this will just be broke... since the .META.
format will have changed (endkeys rather than startkeys). Ain't sure what to
do about that. It'll be at a major version transition.
> 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
