[ 
https://issues.apache.org/jira/browse/HBASE-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168728#comment-13168728
 ] 

jirapos...@reviews.apache.org commented on HBASE-4382:
------------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3190/
-----------------------------------------------------------

(Updated 2011-12-13 21:13:05.977763)


Review request for hbase.


Summary
-------

PART 3 of hbase-4616 
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 addresses bug hbase-4382.
    https://issues.apache.org/jira/browse/hbase-4382


Diffs (updated)
-----

  src/main/java/org/apache/hadoop/hbase/HRegionInfo.java 74cb821 

Diff: https://reviews.apache.org/r/3190/diff


Testing
-------


Thanks,

Alex


                
> 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

        

Reply via email to