Skip to content

[hotfix][doc] Fix invalid sql comments and words in timezone.md #15785

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
hackergin wants to merge 1 commit into from
Closed

[hotfix][doc] Fix invalid sql comments and words in timezone.md #15785

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/content/docs/dev/table/concepts/timezone.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 >}}
Expand Down Expand Up @@ -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.
Expand Down