This is an automated email from the ASF dual-hosted git repository.
jark pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/master by this push:
new 60c7d9e [hotfix][docs] Corrected timezone name and column alignment
(#16103)
60c7d9e is described below
commit 60c7d9e77a6e9d82e0feb33f0d8bc263dddf2fd9
Author: mans2singh <[email protected]>
AuthorDate: Thu Jun 17 11:25:08 2021 -0400
[hotfix][docs] Corrected timezone name and column alignment (#16103)
---
docs/content.zh/docs/dev/table/concepts/timezone.md | 4 ++--
docs/content/docs/dev/table/concepts/timezone.md | 6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/docs/content.zh/docs/dev/table/concepts/timezone.md
b/docs/content.zh/docs/dev/table/concepts/timezone.md
index fac23d9..f1224fc 100644
--- a/docs/content.zh/docs/dev/table/concepts/timezone.md
+++ b/docs/content.zh/docs/dev/table/concepts/timezone.md
@@ -319,7 +319,7 @@ Flink SQL> DESC MyView3;
| window_start | TIMESTAMP(3) | false | | |
|
| window_end | TIMESTAMP(3) | false | | |
|
| window_proctime | TIMESTAMP_LTZ(3) *PROCTIME* | false | | |
|
-| item | STRING | true | | |
|
+| item | STRING | true | | |
|
| max_price | DOUBLE | true | | |
|
+-----------------+-----------------------------+-------+-----+--------+-----------+
```
@@ -542,7 +542,7 @@ Flink SQL> SELECT * FROM MyView5;
Flink SQL支持在 `TIMESTAMP_LTZ`列上定义时间属性， 基于这一特征，Flink SQL 在窗口中使用 `TIMESTAMP` 和
`TIMESTAMP_LTZ` 类型优雅地支持了夏令时。
Flink 使用时间戳的字符格式来分割窗口并通过每条记录对应的 epoch 时间来分配窗口。 这意味着 Flink 窗口开始时间和窗口结束时间使用的是
`TIMESTAMP` 类型（例如: `TUMBLE_START` 和 `TUMBLE_END`）， 窗口的时间属性使用的是 `TIMESTAMP_LTZ`
类型（例如: `TUMBLE_PROCTIME`， `TUMBLE_ROWTIME`）。
-给定一个 tumble window示例， 在 Los_Angele 时区下夏令时从 `2021-03-14 02:00:00` 开始：
+给定一个 tumble window示例， 在 Los_Angeles 时区下夏令时从 `2021-03-14 02:00:00` 开始：
```
long epoch1 = 1615708800000L; // 2021-03-14 00:00:00
long epoch2 = 1615712400000L; // 2021-03-14 01:00:00
diff --git a/docs/content/docs/dev/table/concepts/timezone.md
b/docs/content/docs/dev/table/concepts/timezone.md
index 7ecb9d9..36bacd5 100644
--- a/docs/content/docs/dev/table/concepts/timezone.md
+++ b/docs/content/docs/dev/table/concepts/timezone.md
@@ -120,7 +120,7 @@
tEnv.getConfig.setLocalTimeZone(ZoneId.of("America/Los_Angeles"))
The session time zone is useful in Flink SQL, the main usages are:
### Decide time functions return value
-The following time functions is influenced by the configured time zone.
+The following time functions are influenced by the configured time zone:
* LOCALTIME
* LOCALTIMESTAMP
* CURRENT_DATE
@@ -320,7 +320,7 @@ Flink SQL> DESC MyView3;
| window_start | TIMESTAMP(3) | false | | |
|
| window_end | TIMESTAMP(3) | false | | |
|
| window_proctime | TIMESTAMP_LTZ(3) *PROCTIME* | false | | |
|
-| item | STRING | true | | |
|
+| item | STRING | true | | |
|
| max_price | DOUBLE | true | | |
|
+-----------------+-----------------------------+-------+-----+--------+-----------+
```
@@ -544,7 +544,7 @@ Flink SQL supports defining time attributes on
TIMESTAMP_LTZ column, base on thi
Flink use timestamp literal to split the window and assigns window to data
according to the epoch time of the each row. It means Flink uses `TIMESTAMP`
type for window start and window end (e.g. `TUMBLE_START` and `TUMBLE_END`),
uses `TIMESTAMP_LTZ` for window time attribute (e.g. `TUMBLE_PROCTIME`,
`TUMBLE_ROWTIME`).
-Given a example of tumble window, the DaylightTime in Los_Angele starts at
time 2021-03-14 02:00:00:
+Given an example of tumble window, the DaylightTime in Los_Angeles starts at
time 2021-03-14 02:00:00:
```
long epoch1 = 1615708800000L; // 2021-03-14 00:00:00
long epoch2 = 1615712400000L; // 2021-03-14 01:00:00
