hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10578) For the same row key, the KV in the newest StoreFile should be returned
Date Thu, 20 Feb 2014 23:53:24 GMT

    [ https://issues.apache.org/jira/browse/HBASE-10578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907732#comment-13907732
] 

stack commented on HBASE-10578:
-------------------------------

We have this issue in trunk too.  The patch looks like it'll apply too...

> For the same row key, the KV in the newest StoreFile should be returned
> -----------------------------------------------------------------------
>
>                 Key: HBASE-10578
>                 URL: https://issues.apache.org/jira/browse/HBASE-10578
>             Project: HBase
>          Issue Type: Bug
>          Components: Scanners
>    Affects Versions: 0.89-fb, 0.98.1
>            Reporter: Amitanand Aiyer
>            Assignee: Amitanand Aiyer
>            Priority: Minor
>             Fix For: 0.89-fb
>
>         Attachments: HBASE-10578-v2.patch, HBASE-10578.patch
>
>
> When multiple scanners have the same KV, HBase should pick the "newest" one.
> i.e. pick the KV from the store file with the largest seq id.
> In the KeyValueHeap generalizedSeek implementation, we seem to prefer the "current"
> scanner over the scanners in the heap -- THIS IS WRONG.
> The diff adds a unit test to make sure that bulk loads correctly. And fixes the issue.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message