From 265e46ed1c0b21c8ee7e436af1ef69930918b63c Mon Sep 17 00:00:00 2001 From: jinfeng Date: Tue, 27 Apr 2021 22:00:47 +0800 Subject: [PATCH] [hotfix][doc] Fix invalid sql comment and words in timezone.md --- docs/content/docs/dev/table/concepts/timezone.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/content/docs/dev/table/concepts/timezone.md b/docs/content/docs/dev/table/concepts/timezone.md index dd5d97c726ee3..910b603f89e23 100644 --- a/docs/content/docs/dev/table/concepts/timezone.md +++ b/docs/content/docs/dev/table/concepts/timezone.md @@ -75,13 +75,13 @@ The local time zone defines current session time zone id. You can config the tim {{< tabs "SQL snippets" >}} {{< tab "SQL Client" >}} ```sql -# set to UTC time zone +-- set to UTC time zone Flink SQL> SET table.local-time-zone=UTC; -# set to Shanghai time zone +-- set to Shanghai time zone Flink SQL> SET table.local-time-zone=Asia/Shanghai; -# set to Los_Angeles time zone +-- set to Los_Angeles time zone Flink SQL> SET table.local-time-zone=America/Los_Angeles; ``` {{< /tab >}} @@ -259,7 +259,7 @@ Flink SQL defines process time attribute by function `PROCTIME()`, the function {{< hint info >}} Before Flink 1.13, the function return type of `PROCTIME()` is `TIMESTAMP`, and the return value is the `TIMESTAMP` in UTC time zone, e.g. the wall-clock shows `2021-03-01 12:00:00` at Shanghai, however the `PROCTIME()` displays `2021-03-01 04:00:00` which is wrong. -Flin 1.13 fixes this issue and uses `TIMESTAMP_LTZ` type as return type of `PROCTIME()`, users don't need to deal time zone problems anymore. +Flink 1.13 fixes this issue and uses `TIMESTAMP_LTZ` type as return type of `PROCTIME()`, users don't need to deal time zone problems anymore. {{< /hint >}} The PROCTIME() always represents your local timestamp value, using TIMESTAMP_LTZ type can also support DayLight Saving Time well.