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-15133) Data loss after compaction when a row has more than Integer.MAX_VALUE columns
Date Wed, 10 Feb 2016 17:21:18 GMT

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

Hudson commented on HBASE-15133:
--------------------------------

FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1169 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1169/])
HBASE-15133 Data loss after compaction when a row has more than (apurtell: rev e18b62cb9d5f522d1f86fe9af17f747677e32c19)
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java


> Data loss after compaction when a row has more than Integer.MAX_VALUE columns
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-15133
>                 URL: https://issues.apache.org/jira/browse/HBASE-15133
>             Project: HBase
>          Issue Type: Bug
>          Components: Compaction
>            Reporter: Toshihiro Suzuki
>            Assignee: Toshihiro Suzuki
>             Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.18
>
>         Attachments: HBASE-15133-v1.patch, HBASE-15133.patch, HBASE-15133.patch
>
>
> We have lost the data in our development environment when a row has more than Integer.MAX_VALUE
columns after compaction.
> I think the reason is type of StoreScanner's countPerRow is int.
> https://github.com/apache/hbase/blob/master/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/StoreScanner.java#L67
> After changing the type to long, it seems to be fixed.



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

Mime
View raw message