You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "daicheng (Jira)" <ji...@apache.org> on 2022/04/23 15:52:00 UTC
[jira] [Created] (KUDU-3363) impala get wrong timestamp when scan kudu timestamp with timezone
daicheng created KUDU-3363:
------------------------------
Summary: 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
impala version is 3.1.0-cdh6.1
!35xwYkMIeefwOgMhhBBCCLlXbreIQAghhBBCCCGEkIfivwA62bfllMcqSwAAAABJRU5ErkJggg==|width=451,height=117!
i have set system timezone=Asia/Shanghai:
!AQFTDOCuJy6yAAAAAElFTkSuQmCC|width=548,height=131!
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)
!4LWincd dPO98AAAAASUVORK5CYII=|width=606,height=214!
!pB4HeSMXP4HxPSrGV0Hq0QAAAAASUVORK5CYII=|width=455,height=186!
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 :
!AkLbNoZZQ2JEAAAAAElFTkSuQmCC|width=454,height=144!
*stop 3*
read it with spark (timezone=shanghai),spark read kudu with kudu-client api,here is the result:
!w9CIosotYzYIwAAAABJRU5ErkJggg==|width=543,height=186!
the result is still exactly right。
but read it with impala-shell:
!fQAAAABJRU5ErkJggg==|width=629,height=101!
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.7#820007)