Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 25 Apr 2012 01:52:08 +0000 (UTC)
From: "binlijin (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <2137733990.1293.1335318728363.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1466464129.4339.1335175294869.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-5856) byte <-> String is not consistent
 between HBaseAdmin and HRegionInfo
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HBASE-5856?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1326=
1229#comment-13261229 ]=20

binlijin commented on HBASE-5856:
---------------------------------

@stack
We can get the string(testsplit,\x00\x00\x00\x00\x00\x00\x00\x00,1335169851=
181.79d80fbc6c4f6cfc2cdca8a5310b7223. ) from the web (/table.jsp) or HRegio=
nInfo.getRegionNameAsString(), if we pass the string to web or jruby shell =
or HBaseAdmin.split(String) will get TableNotFoundException.
               =20
> byte <-> String is not consistent between HBaseAdmin and HRegionInfo
> --------------------------------------------------------------------
>
>                 Key: HBASE-5856
>                 URL: https://issues.apache.org/jira/browse/HBASE-5856
>             Project: HBase
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.90.6, 0.92.1
>            Reporter: binlijin
>         Attachments: HBASE-5856-0.92.patch
>
>
> In HBaseAdmin=20
>   public void split(final String tableNameOrRegionName)
>   throws IOException, InterruptedException {
>     split(Bytes.toBytes(tableNameOrRegionName));  // string -> byte=20
>   }
> In HRegionInfo
>   this.regionNameStr =3D Bytes.toStringBinary(this.regionName);  // byte =
-> string
> Should we use Bytes.toBytesBinary in HBaseAdmin =EF=BC=9F

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira