You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Josh Elser (Jira)" <ji...@apache.org> on 2019/12/09 16:41:00 UTC

[jira] [Resolved] (PHOENIX-5603) Phoenix add sybmol 0x00 to first in key

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

Josh Elser resolved PHOENIX-5603.
---------------------------------
    Resolution: Not A Problem

You are describing how the Salted Tables feature in Phoenix works. The salt byte is prefixed onto the rowkey.

Please ask questions on the user mailing list in the future.

> Phoenix add sybmol 0x00 to first in key
> ---------------------------------------
>
>                 Key: PHOENIX-5603
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5603
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0
>         Environment: HDP 3.0 
> hbase 2.0.2.3.1.0.0-78
>            Reporter: Rustam Iksanov
>            Priority: Major
>         Attachments: keyWObyte.jpg, keyWbyte.jpg
>
>
> Phoenix add symbol `0X00` to rowkey in the salted table. If data load without phoenix, where aren't this byte.
> Create table with next script:
> ```CREATE TABLE TKT ("ROWKEY" varchar PRIMARY KEY,
> CREATED bigint);```
>  
> Write data always from spark connector, for example:
> ```df.write.format("org.apache.phoenix.spark").mode("overwrite").option("zkUrl", "zkServAdrs:2181").option("table", "TKT").save()```
>  
> And 2 scan from hbase shell. One table with salt, second similar table without salt.
>  
> Links to similar problem([https://stackoverflow.com/questions/47809243/phoenix-salted-table-rowkey-issue-with-hbase])



--
This message was sent by Atlassian Jira
(v8.3.4#803005)