Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 7 Oct 2014 05:01:34 +0000 (UTC)
From: "Matt Corgan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12743724.1411542881000.205452.1412658094628@Atlassian.JIRA>
In-Reply-To: <JIRA.12743724.1411542881000@Atlassian.JIRA>
References: <JIRA.12743724.1411542881000@Atlassian.JIRA>
 <JIRA.12743724.1411542881201@arcas>
Subject: [jira] [Commented] (HBASE-12078) Missing Data when scanning using
 PREFIX_TREE DATA-BLOCK-ENCODING
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HBASE-12078?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D141=
61467#comment-14161467 ]=20

Matt Corgan commented on HBASE-12078:
-------------------------------------

Wow!  Thank you guys so much for debugging that.  Sorry I was not much help=
 lately.

> Missing Data when scanning using PREFIX_TREE DATA-BLOCK-ENCODING
> ----------------------------------------------------------------
>
>                 Key: HBASE-12078
>                 URL: https://issues.apache.org/jira/browse/HBASE-12078
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.6.1
>         Environment: CentOS 6.3
> hadoop 2.5.0(hdfs)
> hadoop 2.2.0(hbase)
> hbase 0.98.6.1
> sun-jdk 1.7.0_67-b01
>            Reporter: zhangduo
>            Assignee: zhangduo
>            Priority: Critical
>             Fix For: 2.0.0, 0.98.7, 0.99.1
>
>         Attachments: HBASE-12078-0.98.patch, HBASE-12078.patch, HBASE-120=
78_1.patch, prefix_tree_error.patch
>
>
> our row key is combined with two ints, and we found that sometimes when w=
e using only the first int part to scan, the result returned may missing so=
me rows. But when we dump the whole hfile, the row is still there.
> We have written a testcase to reproduce the bug. It works like this:
> put 1-12345
> put 12345-0x01000000
> put 12345-0x01010000
> put 12345-0x02000000
> put 12345-0x02020000
> put 12345-0x03000000
> put 12345-0x03030000
> put 12345-0x04000000
> put 12345-0x04040000
> flush memstore
> then scan using 12345=EF=BC=8Cthe returned row key will be 12345-0x200000=
00(12345-0x10000000 expected)


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)