[ 
https://issues.apache.org/jira/browse/FLINK-26672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17507409#comment-17507409
 ] 

Francesco Guardiani commented on FLINK-26672:
---------------------------------------------

This might be an issue of the to string converter, which we resolved on master. 
Can you try this test with a nightly release? Or if you wait a couple of days, 
a 1.15 RC should be released, you can try with that as well.

> In Table/SQL API, Table configuration ' table.local-time-zone' does not work
> ----------------------------------------------------------------------------
>
>                 Key: FLINK-26672
>                 URL: https://issues.apache.org/jira/browse/FLINK-26672
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / API
>    Affects Versions: 1.13.1
>            Reporter: RuiLin-Zhang
>            Priority: Major
>             Fix For: 1.13.1
>
>
> I created a table structure
> {color:#ff0000}tabEnv.getConfig.getConfiguration.setString("table.local-time-zone",
>  "Asia/Shanghai"){color}
> create table dwd_event_kafka (
> `platform` bigint,
> `ts` bigint,
> `event_ts` as to_timestamp_ltz(ts,3),
> `log_time` bigint,
> `event` integer,
> `page` integer,
> `guid` string,
> `goods_id` bigint,
> `third_class_id` bigint,
> `main_goods_id` bigint,
> `event_time` as to_timestamp_ltz(log_time,3),
> watermark for event_time as event_time - interval '5' second
> ) with (
> 'connector' = 'kafka',
> ...
> )
> > +I[101, 1647402695000, 2022-03-16T03:51:35Z, 1647402698149, 101, 131001, 
> > 22547286, 8005242, 471, 8005242, 2022-03-16T03:51:38.149Z]
> I found is wrong, the output data converted by  to_timestamp_ltz function . I 
> tried to configure {color:#ff0000}"table.local-time-zone"{color} and found it 
> didn't work.
>  
> In Shanghai time zone,the timestamp(1647402695000 ) should be  
> "2022-03-16T11:51:35Z" instead of  "2022-03-16T03:51:35Z"  .
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to