hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2658) REST (stargate) TableRegionModel Regions need to be updated to work w/ new region naming convention from HBASE-2531
Date Wed, 02 Jun 2010 18:43:46 GMT

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

stack commented on HBASE-2658:
------------------------------

Over in hbase-2657 I loosed the below changing it to a startsWith from an equals test:

{code}
        HRegionInfo hri = e.getKey();
        String hriRegionName = hri.getRegionNameAsString();
        String regionName = region.getName();
        if (hriRegionName.startsWith(regionName)) {
{code}

Restore when fix for this here.

> REST (stargate) TableRegionModel Regions need to be updated to work w/ new region naming
convention from HBASE-2531
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-2658
>                 URL: https://issues.apache.org/jira/browse/HBASE-2658
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: Andrew Purtell
>             Fix For: 0.21.0
>
>
> One reason TestTableResource was failing was because comparing region names as strings
was failing because the two below no longer matched.  My guess is that the rest stuff is not
using the new means of constructing region names.  See HBASE-2531
> TestTableResource,,1275503739792.30a45563321be3ec11841b0f1e79d687.
> TestTableResource,,1275503739792

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message