You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "chenrongwei (JIRA)" <ji...@apache.org> on 2016/01/18 03:16:39 UTC
[jira] [Updated] (HBASE-15126) HBaseFsck's checkRegionBoundaries
function set the 'storesFirstKey' was incorrect.
[ https://issues.apache.org/jira/browse/HBASE-15126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
chenrongwei updated HBASE-15126:
--------------------------------
Affects Version/s: 2.0.0
> HBaseFsck's checkRegionBoundaries function set the 'storesFirstKey' was incorrect.
> -----------------------------------------------------------------------------------
>
> Key: HBASE-15126
> URL: https://issues.apache.org/jira/browse/HBASE-15126
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: chenrongwei
> Assignee: chenrongwei
>
> HBaseFsck's checkRegionBoundaries function set the 'currentRegionBoundariesInformation.storesFirstKey' was incorrect.I think it should be set like below,
> currentRegionBoundariesInformation.storesFirstKey = keyOnly(storeFirstKey);
> but current the 'currentRegionBoundariesInformation.storesFirstKey ' is just set to 'storeFirstKey',which will cause to comparator.compare(currentRegionBoundariesInformation.storesFirstKey,
> currentRegionBoundariesInformation.metaFirstKey) get a wrong result. Because it just compared the rowkey's length.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)