You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/16 17:23:00 UTC

[jira] [Resolved] (HBASE-8865) HBase shell split command acts incorrectly with hex split keys.

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

Andrew Kyle Purtell resolved HBASE-8865.
----------------------------------------
    Resolution: Incomplete

> HBase shell split command acts incorrectly with hex split keys.
> ---------------------------------------------------------------
>
>                 Key: HBASE-8865
>                 URL: https://issues.apache.org/jira/browse/HBASE-8865
>             Project: HBase
>          Issue Type: Bug
>          Components: shell, Usability
>    Affects Versions: 0.94.8
>         Environment: Linux
>            Reporter: Ding Haifeng
>            Priority: Major
>         Attachments: 8865.txt
>
>
> When I tried to do a manual region split from HBase shell, I found that split command acts incorrectly with hex split keys. 
> Here is an example.
> I execute hbase(main):003:0> split 'tsdb', "\x00\x00\xC3" .
> While I expect it to split at the 3-byte key "\x00\x00\xC3" , it actually split at a 5-byte key "\x00\x00\xEF\xBF\xBD". 
> I test with more split keys and find some patterns:
> * If the all bytes in the split key represented in hexadecimal are between "\x00" and "\x7F" , it works as expected and split at exactly the key specified.
> * If there are any bytes between "\x80" and "xFF", it works incorrectly. No matter the byte is, it is interpreted as "\xEF\xBF\xBD". Here is another example. Specifying split key "\x00\xA0\x00\xB0" actually splits at "\x00\xEF\xBF\xBD\x00\xEF\xBF\xBD".
> I'm running Hbase 0.94.8, r1485407, both server-side and client-side. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)