You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Amal Joshy (JIRA)" <ji...@apache.org> on 2016/02/17 10:04:18 UTC
[jira] [Updated] (HBASE-15133) Data loss after compaction when a
row has more than Integer.MAXVALUE columns
[ https://issues.apache.org/jira/browse/HBASE-15133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amal Joshy updated HBASE-15133:
-------------------------------
Summary: Data loss after compaction when a row has more than Integer.MAXVALUE columns (was: Data loss after compaction when a row has more than Integer.MAX_VALUE columns)
> Data loss after compaction when a row has more than Integer.MAXVALUE 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)