phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anil <anilk...@gmail.com>
Subject Re: Hbase vs Phienix column names
Date Tue, 11 Dec 2018 08:32:29 GMT
Thanks.

On Tue, 11 Dec 2018 at 11:51, Jaanai Zhang <cloud.poster@gmail.com> wrote:

> The difference since used encode column names that support in 4.10
> version(Also see PHOENIX-1598
> <https://issues.apache.org/jira/browse/PHOENIX-1598>).
> You can config COLUMN_ENCODED_BYTES property to keep the original column
> names in the create table SQL, an example for:
>
> create table test(
>
> id varchar  primary key,
>
> col varchar
>
> )COLUMN_ENCODED_BYTES =0 ;
>
>
>
> ----------------------------------------
>    Jaanai Zhang
>    Best regards!
>
>
>
> Anil <anilklce@gmail.com> 于2018年12月11日周二 下午1:24写道:
>
>> HI,
>>
>> We have upgraded phoenix to Phoenix-4.11.0-cdh5.11.2 from phoenix 4.7.
>>
>> Problem - When a table is created in phoenix, underlying hbase column
>> names and phoenix column names are different. Tables created in 4.7 version
>> looks good. Looks
>>
>> CREATE TABLE TST_TEMP (TID VARCHAR PRIMARY KEY ,PRI VARCHAR,SFLG
>> VARCHAR,PFLG VARCHAR,SOLTO VARCHAR,BILTO VARCHAR) COMPRESSION = 'SNAPPY';
>>
>> 0: jdbc:phoenix:dq-13.labs.> select TID,PRI,SFLG from TST_TEMP limit 2;
>> +-------------+------------+-----------+
>> |   TID       |    PRI     |    SFLG   |
>> +-------------+------------+-----------+
>> | 0060189122  | 0.00       |           |
>> | 0060298478  | 13390.26   |           |
>> +-------------+------------+-----------+
>>
>>
>> hbase(main):011:0> scan 'TST_TEMP', {LIMIT => 2}
>> ROW                                      COLUMN+CELL
>>  0060189122                              column=0:\x00\x00\x00\x00,
>> timestamp=1544296959236, value=x
>>  0060189122                              column=0:\x80\x0B,
>> timestamp=1544296959236, value=0.00
>>  0060298478                              column=0:\x00\x00\x00\x00,
>> timestamp=1544296959236, value=x
>>  0060298478                              column=0:\x80\x0B,
>> timestamp=1544296959236, value=13390.26
>>
>>
>> hbase columns names are completely different than phoenix column names.
>> This change observed only post up-gradation. all existing tables created in
>> earlier versions looks good and alter statements to existing tables also
>> looks good.
>>
>> Is there any workaround to avoid this difference? we could not run hbase
>> mapreduce jobs on hbase tables created  by phoenix. Thanks.
>>
>> Thanks
>>
>>
>>
>>
>>
>>
>>

Mime
View raw message