Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 20 Feb 2014 23:37:19 +0000 (UTC)
From: "Amitanand Aiyer (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12696369.1392931869693.77594.1392939439682@arcas>
In-Reply-To: <JIRA.12696369.1392931869693@arcas>
References: <JIRA.12696369.1392931869693@arcas>
Subject: [jira] [Updated] (HBASE-10578) For the same row key, the KV in the
 newest StoreFile should be returned
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Amitanand Aiyer updated HBASE-10578:
------------------------------------

    Attachment: HBASE-10578-v2.patch

This file is intended to be applied over 0.89-fb.

Not sure why HadoopQA tries to apply this over opensource trunk, and complain about it.

> 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)