[
https://issues.apache.org/jira/browse/HBASE-9559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773400#comment-13773400
]
Sergey Shelukhin commented on HBASE-9559:
-----------------------------------------
Hmm... ts assumption can be invalidated by region movement and clock skew, but
I guess it would work in practice.
But delete assumption I do not understand - right now deletes seem to be
handled only within the same scanner, or am I missing something? Expecting
region delete to be in the same file as region record seems to be pretty
unsafe.
> 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 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
