hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tianying Chang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8044) split/flush/compact/major_compact from hbase shell does not work for region key with \x format
Date Tue, 12 Mar 2013 06:05:14 GMT

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

Tianying Chang commented on HBASE-8044:
---------------------------------------

@jeffery zhong, What is the expectation? Do you mean HBase shell command should not support
the HBase WebUI format for regionName with non-printable chars?

HBASE use toStringBinary to convert the non-printable chars to the current format when the
regionName is displayed on the WebUI, that is why you see the \x00\x05. If the regionName
itself is \0x05, it will not be dispalyed as \0x05, due to the funtion of toStirngBinary.
So as long as you use the regionName shown on the WebUI, this has to be converted back to
bytes using toBytesBinary(). Without this change, we cannot invoke this list of hbase shell
command for a regionName that contains non-printable chars. Our production cluster is using
this feature in 92.  
                
> split/flush/compact/major_compact from hbase shell does not work for region key with
\x format
> ----------------------------------------------------------------------------------------------
>
>                 Key: HBASE-8044
>                 URL: https://issues.apache.org/jira/browse/HBASE-8044
>             Project: HBase
>          Issue Type: Bug
>          Components: Admin
>    Affects Versions: 0.94.5
>            Reporter: Tianying Chang
>            Assignee: Tianying Chang
>             Fix For: 0.95.0, 0.98.0, 0.94.7
>
>         Attachments: 8044.patch, 8044-trunk.txt, 8044-trunk-v2.txt, 8044-v2.patch
>
>
> the conversion between bytes and string is incorrect

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message