You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/11/16 21:23:58 UTC

[jira] [Updated] (HBASE-5969) HRI.getRegionName/AsString are inconsistent for regions with the old encoding scheme

     [ https://issues.apache.org/jira/browse/HBASE-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-5969:
-------------------------
    Affects Version/s:     (was: 0.90.6)
                           (was: 0.92.1)
                       2.0.0

> HRI.getRegionName/AsString are inconsistent for regions with the old encoding scheme
> ------------------------------------------------------------------------------------
>
>                 Key: HBASE-5969
>                 URL: https://issues.apache.org/jira/browse/HBASE-5969
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Jean-Daniel Cryans
>
> HRI.getRegionName and getRegionNameAsString don't give consistent results for regions created with the old encoding scheme. See Aravind's comment in HBASE-5929 on how a region was appended with ".1290583321" when its HRI was queried with getRegionNameAsString and, once passed to HBA, wasn't able to compact it (I checked .META. and it doesn't have that last part so it must come from getRegionName).
> This one might be a little hard to fix if we're already dependent on the broken behavior of getRegionName.



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