Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Wed, 22 Apr 2015 00:33:01 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12522848.1315891646000.68995.1429662781073@Atlassian.JIRA>
In-Reply-To: <JIRA.12522848.1315891646000@Atlassian.JIRA>
References: <JIRA.12522848.1315891646000@Atlassian.JIRA>
 <JIRA.12522848.1315891646992@arcas>
Subject: [jira] [Resolved] (HBASE-4382) Region encoded name is hash of
 tablename + start key + regionid (timestamp); should include end key when
 hashing.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell resolved HBASE-4382.
-----------------------------------
    Resolution: Incomplete

> 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
>              Labels: beginner
>         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 was sent by Atlassian JIRA
(v6.3.4#6332)