[ https://issues.apache.org/jira/browse/HBASE-5563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231860#comment-13231860 ]
Hudson commented on HBASE-5563: ------------------------------- Integrated in HBase-TRUNK-security #140 (See [https://builds.apache.org/job/HBase-TRUNK-security/140/]) HBASE-5563 Add comparison of regionId to HRegionInfo#compareTo (chunhui and jmhsieh) (Revision 1301779) Result = SUCCESS jmhsieh : Files : * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/HRegionInfo.java * /hbase/trunk/src/main/java/org/apache/hadoop/hbase/master/AssignmentManager.java * /hbase/trunk/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegionInfo.java > HRegionInfo#compareTo should compare regionId as well > ----------------------------------------------------- > > Key: HBASE-5563 > URL: https://issues.apache.org/jira/browse/HBASE-5563 > Project: HBase > Issue Type: Bug > Affects Versions: 0.90.5, 0.92.0, 0.94.0, 0.96.0 > Reporter: chunhui shen > Assignee: chunhui shen > Fix For: 0.92.2, 0.94.0, 0.96.0 > > Attachments: HBASE-5563.patch, HBASE-5563v2.patch, > HBASE-5563v2.patch, hbase-5563-v3-0.92.patch, hbase-5563-v3.patch > > > In the one region multi assigned case, we could find that two regions have > the same table name, same startKey, same endKey, and different regionId, so > these two regions are same in TreeMap but different in HashMap. -- 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