You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Naveesh Doolhur (Jira)" <ji...@apache.org> on 2022/07/03 10:59:00 UTC
[jira] [Commented] (KUDU-3363) impala get wrong timestamp when scan kudu timestamp with timezone
[ https://issues.apache.org/jira/browse/KUDU-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17561846#comment-17561846 ]
Naveesh Doolhur commented on KUDU-3363:
---------------------------------------
We have the same issue. Using CDP 7.1.7 SP1.
> impala get wrong timestamp when scan kudu timestamp with timezone
> -----------------------------------------------------------------
>
> Key: KUDU-3363
> URL: https://issues.apache.org/jira/browse/KUDU-3363
> Project: Kudu
> Issue Type: Bug
> Components: impala
> Reporter: daicheng
> Priority: Major
> Attachments: image-2022-04-24-00-01-05-746.png, image-2022-04-24-00-01-37-520.png, image-2022-04-24-00-03-14-467.png, image-2022-04-24-00-04-16-240.png, image-2022-04-24-00-04-52-860.png, image-2022-04-24-00-05-52-086.png, image-2022-04-24-00-07-09-776.png
>
>
> impala version is 3.1.0-cdh6.1
> !image-2022-04-24-00-01-37-520.png|width=504,height=37!
> i have set system timezone=Asia/Shanghai:
> !image-2022-04-24-00-01-05-746.png|width=566,height=91!
> here is the bug:
> *step 1*
> i have parquet file with two columns like below,and read it with impala-shell and spark (timezone=shanghai)
> !image-2022-04-24-00-03-14-467.png|width=666,height=101!
> !image-2022-04-24-00-04-16-240.png|width=551,height=214!
> the result both exactly right。
> *step two*
> create kudu table with impala-shell:
> CREATE TABLE default.test_{_}test{_}_test_time2 (id BIGINT,t TIMESTAMP,PRIMARY KEY (id) ) STORED AS KUDU;
> note: kudu version:1.8
> and insert 2 row into the table with spark :
> !image-2022-04-24-00-04-52-860.png|width=577,height=176!
> *stop 3*
> read it with spark (timezone=shanghai)，spark read kudu table with kudu-client api,here is the result:
> !image-2022-04-24-00-05-52-086.png|width=747,height=246!
> the result is still exactly right。
> but read it with impala-shell:
> !image-2022-04-24-00-07-09-776.png|width=701,height=118!
> the result show late 8hour
> *conclusion*
> it seems like impala timezone didn't work when kudu column type is timestamp, but it work fine in parquet file,I don't know why?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)