[
https://issues.apache.org/jira/browse/HBASE-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168730#comment-13168730
]
Alex Newman commented on HBASE-4382:
------------------------------------
I updated the review for this change, although this should still be considered
a talking point we still need to figure out migrations and a couple of tests. I
am just curious if the approach makes sense.
> Region encoded name is hash of tablename + start key + regionid (timestamp);
> should include end key when hashing.
> -----------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-4382
> URL: https://issues.apache.org/jira/browse/HBASE-4382
> Project: HBase
> Issue Type: Sub-task
> Reporter: stack
> Assignee: Alex Newman
> Labels: noob
> Attachments:
> 0003-Verify-start-and-end-key-are-contained-in-the-encode.patch
>
>
> Seems odd that region encoded name is same for regions if made in same second
> with same start key tough their end keys are different. It can happen in
> unit test. Should mix in the end key when coming up w/ the region name
> encoded name.
--
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
