You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/10/25 22:51:00 UTC

[jira] [Resolved] (HBASE-9559) getRowKeyAtOrBefore may be incorrect for some cases

     [ https://issues.apache.org/jira/browse/HBASE-9559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-9559.
--------------------------
    Resolution: Won't Fix

We don't use getRowAtOrBefore anymore. Removed in hbase-2.

> getRowKeyAtOrBefore may be incorrect for some cases
> ---------------------------------------------------
>
>                 Key: HBASE-9559
>                 URL: https://issues.apache.org/jira/browse/HBASE-9559
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Priority: Minor
>
> See also HBASE-9503. Unless I'm missing something, getRowKeyAtOrBefore does not handle cross-file deletes correctly. It also doesn't handle timestamps between two candidates of the same row if they are in different file (latest by ts is going to be returned).
> It is only used for meta, so it might be working due to low update rate, lack of anomalies and the fact that row values in meta are reasonably persistent, new ones are only added in split.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)