[
https://issues.apache.org/jira/browse/HBASE-5969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281230#comment-13281230
]
Alex Newman commented on HBASE-5969:
------------------------------------
Does it make sense to focus on just fixing getRegionNameAsString for the META
entry in the root table?
> 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: 0.90.6, 0.92.1
> Reporter: Jean-Daniel Cryans
> Assignee: Alex Newman
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
