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

stack commented on HBASE-4115:
------------------------------

Is this right Ryan? I thought the UI already escaped region names that 
comprised binary data?  It used to be the case -- perhaps since broken -- where 
you could copy what was into the UI and then as long as you double-quoted it, 
it'd work.  Here is snippet from shell help:

{code}
If you are using binary keys or values and need to enter them in the shell, use
double-quote'd hexadecimal representation. For example:

  hbase> get 't1', "key\x03\x3f\xcd"
  hbase> get 't1', "key\003\023\011"
  hbase> put 't1', "test\xef\xff", 'f1:', "\x01\x33\x40"
{code}

hbck should print out escaped binary but I would not be surprised if it did 
not... so here you should be able to copy it into shell and double-quote it and 
it'd work (If you single-quote it, the shell does not interpret the bytes IIRC).

So you are pasting actual binary data into the shell?

Thanks.



> HBase shell assign and unassign unusable if region name includes 
> binary-encoded data
> ------------------------------------------------------------------------------------
>
>                 Key: HBASE-4115
>                 URL: https://issues.apache.org/jira/browse/HBASE-4115
>             Project: HBase
>          Issue Type: Bug
>          Components: shell
>    Affects Versions: 0.90.2, 0.90.3
>            Reporter: Ryan Brush
>            Priority: Minor
>         Attachments: admin.patch
>
>
> When using the hbase shell assign and unassign commands, we should be able to 
> copy region names from the hbck utility or the web page hosted by the HMaster 
> process.  But if these names have encoded binary data, they region name won't 
> match and the command will fail.
> This is easily fixed by using Bytes.toBytesBinary on the region name in these 
> commands rather than the raw Bytes.ToBytes.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to