I guess the ‘values’ you means is the underlying instant value fo TIMESTAMP_LTZ
datatype, they are the epoch times which are same in different timezones,
that’s the epoch semantics. The session timezone does not affect the
underlying value, it only affects the display string in a session, you c
I have also tried to set it in flink-conf.yaml, it is visible in Job
Manager Configurations but still NOW() and PROCTIME() are returning values
in UTC.
Thanks and Regards ,
Surendra Lalwani
On Tue, May 10, 2022 at 1:09 PM Surendra Lalwani
wrote:
> Hi Leonard,
>
> Flink Version is 1.13.6 and I
Hi Leonard,
Flink Version is 1.13.6 and I am adding property as follows:
Configuration tconf = tenv.getConfig().getConfiguration();
tconf.setString("table.local-time-zone", "America/Los_Angeles");
tenv.getConfig().setLocalTimeZone(ZoneId.*of*("America/Los_Angeles"));
Thanks and Regards ,
Suren
Hi, Lalwani
Could you share how you set this property and your Flink version?
Best,
Leonard
> 2022年5月10日 下午3:01，Surendra Lalwani 写道：
>
> Hi Team,
>
> I have tried using this property
> table.local-time-zone
>
> But it seems like it is not making any impact, on calling functions like
> PRO
