leonardBang commented on a change in pull request #15753:
URL: https://github.com/apache/flink/pull/15753#discussion_r620954056
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -23,29 +23,29 @@ specific language governing permissions and limitations
under the License.
-->
-## Overview
+## 概述
-Flink provides rich data types for Date and Time, including `DATE`, `TIME`,
`TIMESTAMP`, `TIMESTAMP_LTZ`, `INTERVAL YEAR TO MONTH`, `INTERVAL DAY TO
SECOND` (please see [Date and Time]({{< ref "docs/dev/table/types"
>}}#date-and-time) for detailed information).
-Flink supports setting time zone in session level (please see
[table.local-time-zone]({{< ref
"docs/dev/table/config">}}#table-local-time-zone) for detailed information).
-These timestamp data types and time zone support of Flink make it easy to
process business data across time zones.
+Flink为Date和Time提供了丰富的数据类型, 包括`DATE`, `TIME`, `TIMESTAMP`, `TIMESTAMP_LTZ`,
`INTERVAL YEAR TO MONTH`, `INTERVAL DAY TO SECOND` (更多详情请参考 [Date and Time]({{<
ref "docs/dev/table/types" >}}#date-and-time)).
Review comment:
```suggestion
Flink为日期和时间提供了丰富的数据类型, 包括`DATE`, `TIME`, `TIMESTAMP`, `TIMESTAMP_LTZ`,
`INTERVAL YEAR TO MONTH`, `INTERVAL DAY TO SECOND` (更多详情请参考 [Date and Time]({{<
ref "docs/dev/table/types" >}}#date-and-time)).
```
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -66,22 +66,22 @@ Flink SQL> SELECT * FROM T1;
+---------------------------+
```
-- `TIMESTAMP_LTZ` can be used in cross time zones business because the
absolute time point (e.g. above `4001` milliseconds) describes a same
instantaneous point in different time zones.
-Giving a background that at a same time point, the
`System.currentTimeMillis()` of all machines in the world returns same value
(e.g. the `4001` milliseconds in above example), this is absolute time point
meaning.
+- `TIMESTAMP_LTZ`可以用于跨时区的计算, 因为它是一个基于epoch的绝对时间点(例如: 超过 `4001` 毫秒)
代表的就是不同时区的同一个瞬时时间点.
+用一个场景来描述就是: 在同一个时间点上, 全世界所有的机器上执行`System.currentTimeMillis()`都会返回同样的值. (比如上例中的
`4001` milliseconds), 这就是绝对时间的定义.
-## Time Zone Usage
-The local time zone defines current session time zone id. You can config the
time zone in Sql Client or Applications.
+## 时区的用法
+本地时区定义了当前session所在的时区id. 你可以在Sql client或者Applications中定义.
Review comment:
```suggestion
本地时区定义了当前 session 会话所在的时区. 你可以在 Sql client 中或者应用程序中配置.
```
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -66,22 +66,22 @@ Flink SQL> SELECT * FROM T1;
+---------------------------+
```
-- `TIMESTAMP_LTZ` can be used in cross time zones business because the
absolute time point (e.g. above `4001` milliseconds) describes a same
instantaneous point in different time zones.
-Giving a background that at a same time point, the
`System.currentTimeMillis()` of all machines in the world returns same value
(e.g. the `4001` milliseconds in above example), this is absolute time point
meaning.
+- `TIMESTAMP_LTZ`可以用于跨时区的计算, 因为它是一个基于epoch的绝对时间点(例如: 超过 `4001` 毫秒)
代表的就是不同时区的同一个瞬时时间点.
Review comment:
```suggestion
- `TIMESTAMP_LTZ`可以用于跨时区的计算, 因为它是一个基于epoch的绝对时间点(比如上例中的 `4001` 毫秒)
代表的就是不同时区的同一个绝对时间点.
```
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -105,22 +105,22 @@ Flink SQL> SET table.local-time-zone=America/Los_Angeles;
val envSetting = EnvironmentSettings.newInstance.build
val tEnv = TableEnvironment.create(envSetting)
-// set to UTC time zone
+// 设置为UTC时区
tEnv.getConfig.setLocalTimeZone(ZoneId.of("UTC"))
-// set to Shanghai time zone
+// 设置为上海时区
tEnv.getConfig.setLocalTimeZone(ZoneId.of("Asia/Shanghai"))
-// set to Los_Angeles time zone
+// 设置为Los_Angeles时区
tEnv.getConfig.setLocalTimeZone(ZoneId.of("America/Los_Angeles"))
```
{{< /tab >}}
{{< /tabs >}}
-The session time zone is useful in Flink SQL, the main usages are:
+session的时区设置在Flink SQL中非常有用, 它的主要用法如下:
Review comment:
我们把 `session` 翻译成 `session (会话)`吧，普通用户好理解点
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -368,14 +367,14 @@ Returns the different window start, window end and window
proctime compared to c
```
{{< hint info >}}
-Processing time window is non-deterministic, so each run will get different
windows and different aggregations. The above example is just for explaining
how time zone affects processing time window.
+处理时间窗口是不确定的, 每次运行都会返回不同的窗口和聚合结果. 以上的示例只用于说明时区如何影响处理时间窗口.
{{< /hint >}}
-### Event Time and Time Zone
-Flink supports defining event time attribute on TIMESTAMP column and
TIMESTAMP_LTZ column.
+### 事件时间和时区
+Flink支持在 `TIMESTAMP` 列和 `TIMESTAMP_LTZ` 列上定义时间属性.
Review comment:
```suggestion
Flink支持在 `TIMESTAMP` 列和 `TIMESTAMP_LTZ` 列上定义事件时间属性.
```
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -539,35 +538,34 @@ Returns the different window start, window end and window
rowtime compared to ca
+-------------------------+-------------------------+-------------------------+------+-----------+
```
-## Daylight Saving Time Support
-Flink SQL supports defining time attributes on TIMESTAMP_LTZ column, base on
this, Flink SQL gracefully uses TIMESTAMP and TIMESTAMP_LTZ type in window
processing to support the Daylight Saving Time.
+## 夏令时支持
+Flink SQL支持在 `TIMESTAMP_LTZ`列上定义时间属性, 因此Flink SQL可以在窗口中优雅地使用 `TIMESTAMP` 和
`TIMESTAMP_LTZ` 类型来支持夏令时.
-
-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:
+Flink 使用时间的字符格式来分割窗口并通过row的epoch时间来分配窗口. 这意味着Flink窗口开始时间和窗口结束时间使用的是
`TIMESTAMP` 类型(例如: `TUMBLE_START` 和 `TUMBLE_END`), 将
`TIMESTAMP_LTZ`类型用于窗口的时间属性(例如: `TUMBLE_PROCTIME`, `TUMBLE_ROWTIME`).
+给定一个tumble window示例, 在Los_Angele时区下夏令时从 `2021-03-14 02:00:00` 开始:
```
long epoch1 = 1615708800000L; // 2021-03-14 00:00:00
long epoch2 = 1615712400000L; // 2021-03-14 01:00:00
long epoch3 = 1615716000000L; // 2021-03-14 03:00:00, skip one hour
(2021-03-14 02:00:00)
long epoch4 = 1615719600000L; // 2021-03-14 04:00:00
```
-The tumble window [2021-03-14 00:00:00, 2021-03-14 00:04:00] will collect 3
hours' data in Los_angele time zone, but it collect 4 hours' data in other
non-DST time zones, what user to do is only define time attribute on
TIMESTAMP_LTZ column.
+在Los_angele时区下, tumble window [2021-03-14 00:00:00, 2021-03-14 00:04:00]
将会收集3个小时的数据, 在其他非DST的时区下将会收集4个小时的数据, 用户只需要在 `TIMESTAMP_LTZ` 列上声明时间属性即可.
-All windows in Flink like Hop window, Session window, Cumulative window follow
this way, and all operations in Flink SQL support TIMESTAMP_LTZ well, thus
Flink gracefully supports the Daylight Saving Time zone.
+Flink的所有窗口(如Hop window, Session window, Cumulative window)都会遵循这种方式, Flink
SQL中的所有操作都很好的支持了 `TIMESTAMP_LTZ` , 因此Flink可以非常优雅的支持夏令时.
Review comment:
Flink的所有窗口 (如Hop window, Session window, Cumulative window)
都会遵循这种方式，Flink SQL 中的所有操作都很好的支持了 `TIMESTAMP_LTZ` 类型，因此Flink可以非常优雅的支持夏令时。
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -66,22 +66,22 @@ Flink SQL> SELECT * FROM T1;
+---------------------------+
```
-- `TIMESTAMP_LTZ` can be used in cross time zones business because the
absolute time point (e.g. above `4001` milliseconds) describes a same
instantaneous point in different time zones.
-Giving a background that at a same time point, the
`System.currentTimeMillis()` of all machines in the world returns same value
(e.g. the `4001` milliseconds in above example), this is absolute time point
meaning.
+- `TIMESTAMP_LTZ`可以用于跨时区的计算, 因为它是一个基于epoch的绝对时间点(例如: 超过 `4001` 毫秒)
代表的就是不同时区的同一个瞬时时间点.
+用一个场景来描述就是: 在同一个时间点上, 全世界所有的机器上执行`System.currentTimeMillis()`都会返回同样的值. (比如上例中的
`4001` milliseconds), 这就是绝对时间的定义.
-## Time Zone Usage
-The local time zone defines current session time zone id. You can config the
time zone in Sql Client or Applications.
+## 时区的用法
Review comment:
```suggestion
## 时区的作用
```
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -539,35 +538,34 @@ Returns the different window start, window end and window
rowtime compared to ca
+-------------------------+-------------------------+-------------------------+------+-----------+
```
-## Daylight Saving Time Support
-Flink SQL supports defining time attributes on TIMESTAMP_LTZ column, base on
this, Flink SQL gracefully uses TIMESTAMP and TIMESTAMP_LTZ type in window
processing to support the Daylight Saving Time.
+## 夏令时支持
+Flink SQL支持在 `TIMESTAMP_LTZ`列上定义时间属性, 因此Flink SQL可以在窗口中优雅地使用 `TIMESTAMP` 和
`TIMESTAMP_LTZ` 类型来支持夏令时.
-
-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:
+Flink 使用时间的字符格式来分割窗口并通过row的epoch时间来分配窗口. 这意味着Flink窗口开始时间和窗口结束时间使用的是
`TIMESTAMP` 类型(例如: `TUMBLE_START` 和 `TUMBLE_END`), 将
`TIMESTAMP_LTZ`类型用于窗口的时间属性(例如: `TUMBLE_PROCTIME`, `TUMBLE_ROWTIME`).
+给定一个tumble window示例, 在Los_Angele时区下夏令时从 `2021-03-14 02:00:00` 开始:
```
long epoch1 = 1615708800000L; // 2021-03-14 00:00:00
long epoch2 = 1615712400000L; // 2021-03-14 01:00:00
long epoch3 = 1615716000000L; // 2021-03-14 03:00:00, skip one hour
(2021-03-14 02:00:00)
long epoch4 = 1615719600000L; // 2021-03-14 04:00:00
```
-The tumble window [2021-03-14 00:00:00, 2021-03-14 00:04:00] will collect 3
hours' data in Los_angele time zone, but it collect 4 hours' data in other
non-DST time zones, what user to do is only define time attribute on
TIMESTAMP_LTZ column.
+在Los_angele时区下, tumble window [2021-03-14 00:00:00, 2021-03-14 00:04:00]
将会收集3个小时的数据, 在其他非DST的时区下将会收集4个小时的数据, 用户只需要在 `TIMESTAMP_LTZ` 列上声明时间属性即可.
-All windows in Flink like Hop window, Session window, Cumulative window follow
this way, and all operations in Flink SQL support TIMESTAMP_LTZ well, thus
Flink gracefully supports the Daylight Saving Time zone.
+Flink的所有窗口(如Hop window, Session window, Cumulative window)都会遵循这种方式, Flink
SQL中的所有操作都很好的支持了 `TIMESTAMP_LTZ` , 因此Flink可以非常优雅的支持夏令时.
-## Difference between Batch and Streaming Mode
-The following time functions:
+## Batch模式和Streaming模式的区别
+以下函数:
* LOCALTIME
* LOCALTIMESTAMP
* CURRENT_DATE
* CURRENT_TIME
* CURRENT_TIMESTAMP
* NOW()
-Flink evaluates their values according to execution mode. They are evaluated
for each record in streaming mode. But in batch mode, they are evaluated once
as the query starts and uses the same result for every row.
+Flink 会根据执行模式来进行不同计算. 在Streaming模式下会为每条记录都计算出一个值, 但在Batch模式下, 只会在query开始时计算一次,
所有行都使用相同的结果.
Review comment:
```suggestion
Flink 会根据执行模式来进行不同计算， 在 Streaming 模式下这些函数是每条记录都会计算一次，但在 Batch 模式下， 只会在 query
开始时计算一次，所有记录都使用相同的结果。
```
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -23,29 +23,29 @@ specific language governing permissions and limitations
under the License.
-->
-## Overview
+## 概述
-Flink provides rich data types for Date and Time, including `DATE`, `TIME`,
`TIMESTAMP`, `TIMESTAMP_LTZ`, `INTERVAL YEAR TO MONTH`, `INTERVAL DAY TO
SECOND` (please see [Date and Time]({{< ref "docs/dev/table/types"
>}}#date-and-time) for detailed information).
-Flink supports setting time zone in session level (please see
[table.local-time-zone]({{< ref
"docs/dev/table/config">}}#table-local-time-zone) for detailed information).
-These timestamp data types and time zone support of Flink make it easy to
process business data across time zones.
+Flink为Date和Time提供了丰富的数据类型, 包括`DATE`, `TIME`, `TIMESTAMP`, `TIMESTAMP_LTZ`,
`INTERVAL YEAR TO MONTH`, `INTERVAL DAY TO SECOND` (更多详情请参考 [Date and Time]({{<
ref "docs/dev/table/types" >}}#date-and-time)).
+Flink支持在session级别设置时区(更多详情请参考 [table.local-time-zone]({{< ref
"docs/dev/table/config">}}#table-local-time-zone)).
+Flink对多种时间类型和时区的支持使得跨时区的数据处理变得非常容易.
Review comment:
```suggestion
Flink 支持在 session 级别设置时区(更多详情请参考 [table.local-time-zone]({{< ref
"docs/dev/table/config">}}#table-local-time-zone)).
Flink 对多种时间类型和时区的支持使得跨时区的数据处理变得非常容易.
```
中文中的英文单词前后加个空格，文中的都可以一起改下
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -66,22 +66,22 @@ Flink SQL> SELECT * FROM T1;
+---------------------------+
```
-- `TIMESTAMP_LTZ` can be used in cross time zones business because the
absolute time point (e.g. above `4001` milliseconds) describes a same
instantaneous point in different time zones.
-Giving a background that at a same time point, the
`System.currentTimeMillis()` of all machines in the world returns same value
(e.g. the `4001` milliseconds in above example), this is absolute time point
meaning.
+- `TIMESTAMP_LTZ`可以用于跨时区的计算, 因为它是一个基于epoch的绝对时间点(例如: 超过 `4001` 毫秒)
代表的就是不同时区的同一个瞬时时间点.
+用一个场景来描述就是: 在同一个时间点上, 全世界所有的机器上执行`System.currentTimeMillis()`都会返回同样的值. (比如上例中的
`4001` milliseconds), 这就是绝对时间的定义.
Review comment:
```suggestion
补充一个背景知识: 在同一个时间点, 全世界所有的机器上执行`System.currentTimeMillis()`都会返回同样的值. (比如上例中的
`4001` milliseconds), 这就是绝对时间的定义.
```
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -539,35 +538,34 @@ Returns the different window start, window end and window
rowtime compared to ca
+-------------------------+-------------------------+-------------------------+------+-----------+
```
-## Daylight Saving Time Support
-Flink SQL supports defining time attributes on TIMESTAMP_LTZ column, base on
this, Flink SQL gracefully uses TIMESTAMP and TIMESTAMP_LTZ type in window
processing to support the Daylight Saving Time.
+## 夏令时支持
+Flink SQL支持在 `TIMESTAMP_LTZ`列上定义时间属性, 因此Flink SQL可以在窗口中优雅地使用 `TIMESTAMP` 和
`TIMESTAMP_LTZ` 类型来支持夏令时.
Review comment:
```suggestion
Flink SQL支持在 `TIMESTAMP_LTZ`列上定义时间属性， 基于这一特征，Flink SQL 在窗口中使用 `TIMESTAMP` 和
`TIMESTAMP_LTZ` 类型优雅地支持了夏令时。
```
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -249,20 +249,19 @@ Flink SQL> SELECT * FROM MyView3;
+-------------------------+---------------------------+-------------------------+-------------------------+-------------------------------+
```
-## Time Attribute and Time Zone
+## 时间属性和时区
+更多时间属性相关的详细介绍, 请参考 [Time Attribute]({{< ref
"docs/dev/table/concepts/time_attributes">}}#时间属性).
-Please see [Time Attribute]({{< ref
"docs/dev/table/concepts/time_attributes">}}#时间属性) for more information about
time attribute.
-
-### Processing Time and Time Zone
-Flink SQL defines process time attribute by function `PROCTIME()`, the
function return type is `TIMESTAMP_LTZ`.
+### 处理时间和时区
+Flink SQL 使用函数 `PROCTIME()` 来定义处理时间属性, 该函数返回的类型是 `TIMESTAMP_LTZ`.
{{< 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.
+在Flink1.13之前, `PROCTIME()` 函数返回的类型是 `TIMESTAMP`, 返回值是UTC时区下的 `TIMESTAMP`.
+例如: 当上海的时间为 `2021-03-01 12:00:00` 时, `PROCTIME()` 显示的时间却是`2021-03-01
04:00:00`, 因此是错的.
+这个问题在Flink 1.13中修复了, 因此用户不用再去处理时区的问题了.
{{< /hint >}}
-The PROCTIME() always represents your local timestamp value, using
TIMESTAMP_LTZ type can also support DayLight Saving Time well.
+`PROCTIME()` 返回的时本地时区的时间, 使用 `TIMESTAMP_LTZ` 类型也可以支持夏令时时间.
Review comment:
minor:
```suggestion
`PROCTIME()` 返回的是本地时区的时间, 使用 `TIMESTAMP_LTZ` 类型也可以支持夏令时时间.
```
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -368,14 +367,14 @@ Returns the different window start, window end and window
proctime compared to c
```
{{< hint info >}}
-Processing time window is non-deterministic, so each run will get different
windows and different aggregations. The above example is just for explaining
how time zone affects processing time window.
+处理时间窗口是不确定的, 每次运行都会返回不同的窗口和聚合结果. 以上的示例只用于说明时区如何影响处理时间窗口.
{{< /hint >}}
-### Event Time and Time Zone
-Flink supports defining event time attribute on TIMESTAMP column and
TIMESTAMP_LTZ column.
+### 事件时间和时区
+Flink支持在 `TIMESTAMP` 列和 `TIMESTAMP_LTZ` 列上定义时间属性.
-#### Event Time Attribute on TIMESTAMP
-If the timestamp data in the source is represented as
year-month-day-hour-minute-second, usually a string value without time-zone
information, e.g. `2020-04-15 20:13:40.564`, it's recommended to define the
event time attribute as a `TIMESTAMP` column:
+#### TIMESTAMP 上的事件时间属性
+如果source中的时间用于表示年-月-日-小时-分钟-秒, 通常是一个不带时区的字符串, 例如: `2020-04-15 20:13:40.564`.
通常建议在一个 `TIMESTAMP` 列上定义事件时间属性.
Review comment:
```suggestion
如果source中的时间用于表示年-月-日-小时-分钟-秒, 通常是一个不带时区的字符串, 例如: `2020-04-15
20:13:40.564`。推荐在 `TIMESTAMP` 列上定义事件时间属性。
```
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -249,20 +249,19 @@ Flink SQL> SELECT * FROM MyView3;
+-------------------------+---------------------------+-------------------------+-------------------------+-------------------------------+
```
-## Time Attribute and Time Zone
+## 时间属性和时区
+更多时间属性相关的详细介绍, 请参考 [Time Attribute]({{< ref
"docs/dev/table/concepts/time_attributes">}}#时间属性).
-Please see [Time Attribute]({{< ref
"docs/dev/table/concepts/time_attributes">}}#时间属性) for more information about
time attribute.
-
-### Processing Time and Time Zone
-Flink SQL defines process time attribute by function `PROCTIME()`, the
function return type is `TIMESTAMP_LTZ`.
+### 处理时间和时区
+Flink SQL 使用函数 `PROCTIME()` 来定义处理时间属性, 该函数返回的类型是 `TIMESTAMP_LTZ`.
{{< 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.
+在Flink1.13之前, `PROCTIME()` 函数返回的类型是 `TIMESTAMP`, 返回值是UTC时区下的 `TIMESTAMP`.
+例如: 当上海的时间为 `2021-03-01 12:00:00` 时, `PROCTIME()` 显示的时间却是`2021-03-01
04:00:00`, 因此是错的.
Review comment:
```suggestion
例如: 当上海的时间为 `2021-03-01 12:00:00` 时, `PROCTIME()` 显示的时间却是错误的`2021-03-01
04:00:00`.
```
##########
File path: docs/content.zh/docs/dev/table/concepts/timezone.md
##########
@@ -457,8 +456,8 @@ Returns the same window start, window end and window
rowtime compared to calcula
+-------------------------+-------------------------+-------------------------+------+-----------+
```
-#### Event Time Attribute on TIMESTAMP_LTZ
-If the timestamp data in the source is represented as a epoch time, usually a
long value, e.g. `1618989564564`, it's recommended to define event time
attribute as a `TIMESTAMP_LTZ` column.
+#### TIMESTAMP_LTZ 上的事件时间属性
+如果source中的时间为一个epoch时间, 通常是一个long值, 例如: `1618989564564`, 建议将event time属性定义为
`TIMESTAMP_LTZ` 列.
Review comment:
```suggestion
如果source中的时间为一个epoch时间, 通常是一个long值， 例如: `1618989564564`， 推荐将事件时间属性定义在
`TIMESTAMP_LTZ` 列上。
```
中文里标点符号，我们都使用中文的吧，文中的可以一起改下
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
