hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12078) Missing Data when scanning using PREFIX_TREE DATA-BLOCK-ENCODING
Date Thu, 02 Oct 2014 03:27:36 GMT

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

Hudson commented on HBASE-12078:
--------------------------------

FAILURE: Integrated in HBase-1.0 #258 (See [https://builds.apache.org/job/HBase-1.0/258/])
HBASE-12078 Missing Data when scanning using PREFIX_TREE DATA-BLOCK-ENCODING (apurtell: rev
947f09a62bb2a2e7ed9d7237881e317f2d40cd76)
* hbase-prefix-tree/src/main/java/org/apache/hadoop/hbase/codec/prefixtree/decode/row/RowNodeReader.java
* hbase-prefix-tree/src/test/java/org/apache/hadoop/hbase/codec/prefixtree/row/TestRowData.java
* hbase-prefix-tree/src/test/java/org/apache/hadoop/hbase/codec/prefixtree/row/data/TestRowDataSearchWithPrefix.java
* hbase-prefix-tree/src/main/java/org/apache/hadoop/hbase/codec/prefixtree/decode/PrefixTreeArraySearcher.java
* hbase-prefix-tree/src/test/java/org/apache/hadoop/hbase/codec/prefixtree/row/TestPrefixTreeSearcher.java


> 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-12078_1.patch,
prefix_tree_error.patch
>
>
> our row key is combined with two ints, and we found that sometimes when we using only
the first int part to scan, the result returned may missing some 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,the returned row key will be 12345-0x20000000(12345-0x10000000
expected)



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

Mime
View raw message