You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2022/06/15 09:17:26 UTC
[GitHub] [flink] cason0126 opened a new pull request, #19964: [FLINK-27291][docs-zh] Translate the "List of Data Types" section of…
cason0126 opened a new pull request, #19964:
URL: https://github.com/apache/flink/pull/19964
… "Data Types" in to Chinese
<!--
*Thank you very much for contributing to Apache Flink - we are happy that you want to help us improve Flink. To help the community review your contribution in the best possible way, please go through the checklist below, which will get the contribution into a shape in which it can be best reviewed.*
*Please understand that we do not do this to make contributions to Flink a hassle. In order to uphold a high standard of quality for code contributions, while at the same time managing a large number of contributions, we need contributors to prepare the contributions well, and give reviewers enough contextual information for the review. Please also understand that contributions that do not follow this guide will take longer to review and thus typically be picked up with lower priority by the community.*
## Contribution Checklist
- Make sure that the pull request corresponds to a [JIRA issue](https://issues.apache.org/jira/projects/FLINK/issues). Exceptions are made for typos in JavaDoc or documentation files, which need no JIRA issue.
- Name the pull request in the form "[FLINK-XXXX] [component] Title of the pull request", where *FLINK-XXXX* should be replaced by the actual issue number. Skip *component* if you are unsure about which is the best component.
Typo fixes that have no associated JIRA issue should be named following this pattern: `[hotfix] [docs] Fix typo in event time introduction` or `[hotfix] [javadocs] Expand JavaDoc for PuncuatedWatermarkGenerator`.
- Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review.
- Make sure that the change passes the automated tests, i.e., `mvn clean verify` passes. You can set up Azure Pipelines CI to do that following [this guide](https://cwiki.apache.org/confluence/display/FLINK/Azure+Pipelines#AzurePipelines-Tutorial:SettingupAzurePipelinesforaforkoftheFlinkrepository).
- Each pull request should address only one issue, not mix up code from multiple issues.
- Each commit in the pull request has a meaningful commit message (including the JIRA id)
- Once all items of the checklist are addressed, remove the above text and this checklist, leaving only the filled out template below.
**(The sections below can be removed for hotfixes of typos)**
-->
## What is the purpose of the change
Translate the "List of Data Types" section in Data Types Into Chinese
The url is https://nightlies.apache.org/flink/flink-docs-master/zh/docs/dev/table/types/#list-of-data-types
## Brief change log
- *Translate flink/docs/content.zh/docs/dev/table/types.md*
## Verifying this change
Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
*(Please pick either of the following options)*
This change is a trivial rework / code cleanup without any test coverage.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / no) ：no
- The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / no)：no
- The serializers: (yes / no / don't know)：no
- The runtime per-record code paths (performance sensitive): (yes / no / don't know)：no
- Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)：no
- The S3 file system connector: (yes / no / don't know)：no
## Documentation
- Does this pull request introduce a new feature? (yes / no) ：no
- If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)：no
--
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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] cason0126 commented on pull request #19964: [FLINK-27291][docs-zh] Translate the "List of Data Types" section of…
Posted by GitBox <gi...@apache.org>.
cason0126 commented on PR #19964:
URL: https://github.com/apache/flink/pull/19964#issuecomment-1162569104
>
translating '（both inclusive）' will catch the Chinese reader's attention more than just using '[' and ']' .
I agree with that . catche the attention
--
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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] cason0126 closed pull request #19964: [FLINK-27291][docs-zh] Translate the "List of Data Types" section of…
Posted by "cason0126 (via GitHub)" <gi...@apache.org>.
cason0126 closed pull request #19964: [FLINK-27291][docs-zh] Translate the "List of Data Types" section of…
URL: https://github.com/apache/flink/pull/19964
--
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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] ChengkaiYang2022 commented on a diff in pull request #19964: [FLINK-27291][docs-zh] Translate the "List of Data Types" section of…
Posted by GitBox <gi...@apache.org>.
ChengkaiYang2022 commented on code in PR #19964:
URL: https://github.com/apache/flink/pull/19964#discussion_r901187712
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -686,55 +669,50 @@ TIME(p)
DataTypes.TIME(p)
```
-**Bridging to JVM Types**
+**JVM Types桥接**
-| Java Type | Input | Output | Remarks |
-|:---------------------|:-----:|:------:|:----------------------------------------------------|
-|`java.time.LocalTime` | X | X | *Default* |
-|`java.sql.Time` | X | X | |
-|`java.lang.Integer` | X | X | Describes the number of milliseconds of the day. |
-|`int` | X | (X) | Describes the number of milliseconds of the day.<br>Output only if type is not nullable. |
-|`java.lang.Long` | X | X | Describes the number of nanoseconds of the day. |
-|`long` | X | (X) | Describes the number of nanoseconds of the day.<br>Output only if type is not nullable. |
+| Java Type | 输入 | 输出 | 备注 |
+|:---------------------|:-----:|:------:|:----------------------------------------------------------------------------------------|
+|`java.time.LocalTime` | X | X | *默认* |
+|`java.sql.Time` | X | X | |
+|`java.lang.Integer` | X | X | 描述一天中的毫秒数。 |
+|`int` | X | (X) | 描述一天中的毫秒数。<br>仅当类型不可为空时才输出。 |
+|`java.lang.Long` | X | X | 描述一天中的纳秒数。 |
+|`long` | X | (X) | 描述一天中的纳秒数。<br>仅当类型不可为空时才输出。 |
{{< /tab >}}
{{< tab "Python" >}}
```python
DataTypes.TIME(p)
```
-<span class="label label-danger">Attention</span> The `precision` specified in `DataTypes.TIME(p)` must be `0` currently.
+<span class="label label-danger">请注意</span> 当前，`DataTypes.TIME(p)` 中指定的 `precision` 必须为 `0`。
{{< /tab >}}
{{< /tabs >}}
-The type can be declared using `TIME(p)` where `p` is the number of digits of fractional
-seconds (*precision*). `p` must have a value between `0` and `9` (both inclusive). If no
-precision is specified, `p` is equal to `0`.
+可以使用 `TIME(p)` 声明该类型，其中 `p` 是小数秒的位数（精度）。 p 的取值范围为[`0`,`9`]。 如果未指定精度，则 p 等于 0。
#### `TIMESTAMP`
-Data type of a timestamp *without* time zone consisting of `year-month-day hour:minute:second[.fractional]`
-with up to nanosecond precision and values ranging from `0000-01-01 00:00:00.000000000` to
-`9999-12-31 23:59:59.999999999`.
+有时区的时间类型，由 `年-月-日 小时:分钟:秒[.fractional]`组成，具有高达纳秒的精度，范围从`0000-01-01 00:00:00.000000000`到 `9999-12-31 23:59:59.999999999`。
Review Comment:
how about 具有高达纳秒的精度 -> 可达到纳秒级别的精度 ?
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -686,55 +669,50 @@ TIME(p)
DataTypes.TIME(p)
```
-**Bridging to JVM Types**
+**JVM Types桥接**
-| Java Type | Input | Output | Remarks |
-|:---------------------|:-----:|:------:|:----------------------------------------------------|
-|`java.time.LocalTime` | X | X | *Default* |
-|`java.sql.Time` | X | X | |
-|`java.lang.Integer` | X | X | Describes the number of milliseconds of the day. |
-|`int` | X | (X) | Describes the number of milliseconds of the day.<br>Output only if type is not nullable. |
-|`java.lang.Long` | X | X | Describes the number of nanoseconds of the day. |
-|`long` | X | (X) | Describes the number of nanoseconds of the day.<br>Output only if type is not nullable. |
+| Java Type | 输入 | 输出 | 备注 |
+|:---------------------|:-----:|:------:|:----------------------------------------------------------------------------------------|
+|`java.time.LocalTime` | X | X | *默认* |
+|`java.sql.Time` | X | X | |
+|`java.lang.Integer` | X | X | 描述一天中的毫秒数。 |
+|`int` | X | (X) | 描述一天中的毫秒数。<br>仅当类型不可为空时才输出。 |
+|`java.lang.Long` | X | X | 描述一天中的纳秒数。 |
+|`long` | X | (X) | 描述一天中的纳秒数。<br>仅当类型不可为空时才输出。 |
{{< /tab >}}
{{< tab "Python" >}}
```python
DataTypes.TIME(p)
```
-<span class="label label-danger">Attention</span> The `precision` specified in `DataTypes.TIME(p)` must be `0` currently.
+<span class="label label-danger">请注意</span> 当前，`DataTypes.TIME(p)` 中指定的 `precision` 必须为 `0`。
Review Comment:
precision? Maybe we should translate this term?
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -826,42 +798,37 @@ Not supported.
{{< tabs "timestamps" >}}
{{< tab "SQL/Java/Scala" >}}
-The type can be declared using `TIMESTAMP(p) WITH TIME ZONE` where `p` is the number of digits of
-fractional seconds (*precision*). `p` must have a value between `0` and `9` (both inclusive). If no
-precision is specified, `p` is equal to `6`.
{{< /tab >}}
{{< tab "Python" >}}
{{< /tab >}}
{{< /tabs >}}
+可以使用 `TIMESTAMP(p) WITH TIME ZONE` 声明该类型，其中 `p` 是小数秒的位数（*精度*）。 `p` 取值范围为[`0`,`9`]。如果不指定精度，p 等于 6。
+
#### `TIMESTAMP_LTZ`
-Data type of a timestamp *with local* time zone consisting of `year-month-day hour:minute:second[.fractional] zone`
-with up to nanosecond precision and values ranging from `0000-01-01 00:00:00.000000000 +14:59` to
-`9999-12-31 23:59:59.999999999 -14:59`.
+时间戳的数据类型 *带有本地*时区，格式为`年-月-日 时:分:秒[.fractional] zone` ，精度高达纳秒，值范围从 `0000-01-01 00:00:00.000000000 +14:59` 到 `9999-12-31 23:59:59.999999999 -14:59`。
Review Comment:
时间戳的数据类型 *带有本地*时区，格式为`年-月-日 时:分:秒[.fractional] zone`
->
*带有本地* 时区的时间戳数据类型 ，其格式为 `年-月-日 时:分:秒[.fractional] zone`
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -826,42 +798,37 @@ Not supported.
{{< tabs "timestamps" >}}
{{< tab "SQL/Java/Scala" >}}
-The type can be declared using `TIMESTAMP(p) WITH TIME ZONE` where `p` is the number of digits of
-fractional seconds (*precision*). `p` must have a value between `0` and `9` (both inclusive). If no
-precision is specified, `p` is equal to `6`.
{{< /tab >}}
{{< tab "Python" >}}
{{< /tab >}}
{{< /tabs >}}
+可以使用 `TIMESTAMP(p) WITH TIME ZONE` 声明该类型，其中 `p` 是小数秒的位数（*精度*）。 `p` 取值范围为[`0`,`9`]。如果不指定精度，p 等于 6。
+
#### `TIMESTAMP_LTZ`
-Data type of a timestamp *with local* time zone consisting of `year-month-day hour:minute:second[.fractional] zone`
-with up to nanosecond precision and values ranging from `0000-01-01 00:00:00.000000000 +14:59` to
-`9999-12-31 23:59:59.999999999 -14:59`.
+时间戳的数据类型 *带有本地*时区，格式为`年-月-日 时:分:秒[.fractional] zone` ，精度高达纳秒，值范围从 `0000-01-01 00:00:00.000000000 +14:59` 到 `9999-12-31 23:59:59.999999999 -14:59`。
{{< tabs "timestamps" >}}
{{< tab "SQL/Java/Scala" >}}
-Leap seconds (`23:59:60` and `23:59:61`) are not supported as the semantics are closer to `java.time.OffsetDateTime`.
-Compared to `TIMESTAMP WITH TIME ZONE`, the time zone offset information is not stored physically
-in every datum. Instead, the type assumes `java.time.Instant` semantics in UTC time zone at
-the edges of the table ecosystem. Every datum is interpreted in the local time zone configured in
-the current session for computation and visualization.
+不支持闰秒（`23:59:60` 和 `23:59:61`），其语义更接近 `java.time.OffsetDateTime`。
+
+与`TIMESTAMP WITH TIME ZONE`相比，时区偏移信息没有物理存储在每个数据中。 相反，该类型在 UTC 时区假定为 `java.time.Instant`的语义处于 Table生态系统的边缘。
+每个数据都在配置的本地时区中解释 当前会话用于计算和可视化。
Review Comment:
每个数据都在配置的本地时区中解释 当前会话用于计算和可视化。
This line is a little confusing and people who read it may find it hard to understand, could you be more specific?
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -657,22 +640,22 @@ DataTypes.DATE()
#### `TIME`
-Data type of a time *without* time zone consisting of `hour:minute:second[.fractional]` with
-up to nanosecond precision and values ranging from `00:00:00.000000000` to
-`23:59:59.999999999`.
+无时区的时间类型，包括 `小时:分钟:秒[.fractional]`，精度可达纳秒，取值范围为` 00:00:00.000000000` 到 `23:59:59.999999999`。
+
{{< tabs "time" >}}
{{< tab "SQL/Java/Scala" >}}
-Compared to the SQL standard, leap seconds (`23:59:60` and `23:59:61`) are not supported as
-the semantics are closer to `java.time.LocalTime`. A time *with* time zone is not provided.
+与SQL标准相比，不支持leap秒（23:59:60和23:59:61），因为语义更接近java.time.LocalTime。没有提供带时区的时间。
Review Comment:
leap?
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -826,42 +798,37 @@ Not supported.
{{< tabs "timestamps" >}}
{{< tab "SQL/Java/Scala" >}}
-The type can be declared using `TIMESTAMP(p) WITH TIME ZONE` where `p` is the number of digits of
-fractional seconds (*precision*). `p` must have a value between `0` and `9` (both inclusive). If no
-precision is specified, `p` is equal to `6`.
{{< /tab >}}
{{< tab "Python" >}}
{{< /tab >}}
{{< /tabs >}}
+可以使用 `TIMESTAMP(p) WITH TIME ZONE` 声明该类型，其中 `p` 是小数秒的位数（*精度*）。 `p` 取值范围为[`0`,`9`]。如果不指定精度，p 等于 6。
Review Comment:
小数秒？
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -809,12 +781,12 @@ TIMESTAMP(p) WITH TIME ZONE
DataTypes.TIMESTAMP_WITH_TIME_ZONE(p)
```
-**Bridging to JVM Types**
+**JVM Types桥接**
-| Java Type | Input | Output | Remarks |
-|:--------------------------|:-----:|:------:|:---------------------|
-|`java.time.OffsetDateTime` | X | X | *Default* |
-|`java.time.ZonedDateTime` | X | | Ignores the zone ID. |
+| Java Type | 输入 | 输出 | 备注 |
+|:--------------------------|:-----:|:------:|:--------|
+|`java.time.OffsetDateTime` | X | X | *默认* |
+|`java.time.ZonedDateTime` | X | | 忽略时区ID. |
Review Comment:
. -> 。
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -826,42 +798,37 @@ Not supported.
{{< tabs "timestamps" >}}
{{< tab "SQL/Java/Scala" >}}
-The type can be declared using `TIMESTAMP(p) WITH TIME ZONE` where `p` is the number of digits of
-fractional seconds (*precision*). `p` must have a value between `0` and `9` (both inclusive). If no
-precision is specified, `p` is equal to `6`.
{{< /tab >}}
{{< tab "Python" >}}
{{< /tab >}}
{{< /tabs >}}
+可以使用 `TIMESTAMP(p) WITH TIME ZONE` 声明该类型，其中 `p` 是小数秒的位数（*精度*）。 `p` 取值范围为[`0`,`9`]。如果不指定精度，p 等于 6。
+
#### `TIMESTAMP_LTZ`
-Data type of a timestamp *with local* time zone consisting of `year-month-day hour:minute:second[.fractional] zone`
-with up to nanosecond precision and values ranging from `0000-01-01 00:00:00.000000000 +14:59` to
-`9999-12-31 23:59:59.999999999 -14:59`.
+时间戳的数据类型 *带有本地*时区，格式为`年-月-日 时:分:秒[.fractional] zone` ，精度高达纳秒，值范围从 `0000-01-01 00:00:00.000000000 +14:59` 到 `9999-12-31 23:59:59.999999999 -14:59`。
{{< tabs "timestamps" >}}
{{< tab "SQL/Java/Scala" >}}
-Leap seconds (`23:59:60` and `23:59:61`) are not supported as the semantics are closer to `java.time.OffsetDateTime`.
-Compared to `TIMESTAMP WITH TIME ZONE`, the time zone offset information is not stored physically
-in every datum. Instead, the type assumes `java.time.Instant` semantics in UTC time zone at
-the edges of the table ecosystem. Every datum is interpreted in the local time zone configured in
-the current session for computation and visualization.
+不支持闰秒（`23:59:60` 和 `23:59:61`），其语义更接近 `java.time.OffsetDateTime`。
+
+与`TIMESTAMP WITH TIME ZONE`相比，时区偏移信息没有物理存储在每个数据中。 相反，该类型在 UTC 时区假定为 `java.time.Instant`的语义处于 Table生态系统的边缘。
+每个数据都在配置的本地时区中解释 当前会话用于计算和可视化。
+
{{< /tab >}}
{{< tab "Python" >}}
-Leap seconds (`23:59:60` and `23:59:61`) are not supported.
-Compared to `TIMESTAMP WITH TIME ZONE`, the time zone offset information is not stored physically
-in every datum.
-Every datum is interpreted in the local time zone configured in the current session for computation and visualization.
+不支持闰秒（`23:59:60` 和 `23:59:61`）。
+与`TIMESTAMP WITH TIME ZONE`相比，时区偏移信息没有物理存储 在每个数据中。每个数据都在当前会话中配置的本地时区进行解释，以进行计算和可视化。
Review Comment:
时区偏移信息没有物理存储 在每个数据中。
->
时区偏移信息没有物理存储在每条数据中。
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -1095,22 +1049,17 @@ DataTypes.ARRAY(t)
{{< /tab >}}
{{< /tabs >}}
-The type can be declared using `ARRAY<t>` where `t` is the data type of the contained
-elements.
-`t ARRAY` is a synonym for being closer to the SQL standard. For example, `INT ARRAY` is
-equivalent to `ARRAY<INT>`.
+可以使用 `ARRAY<t>` 声明类型，其中 `t` 是包含的数据类型元素。
Review Comment:
其中 `t` 是包含的数据类型元素。
->
`t` 是其中元素的数据类型。
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -1095,22 +1049,17 @@ DataTypes.ARRAY(t)
{{< /tab >}}
{{< /tabs >}}
-The type can be declared using `ARRAY<t>` where `t` is the data type of the contained
-elements.
-`t ARRAY` is a synonym for being closer to the SQL standard. For example, `INT ARRAY` is
-equivalent to `ARRAY<INT>`.
+可以使用 `ARRAY<t>` 声明类型，其中 `t` 是包含的数据类型元素。
+`t ARRAY` 是更接近 SQL 标准的同义词。 例如，`INT ARRAY` 是相当于`ARRAY<INT>`。
Review Comment:
`t ARRAY` 是更接近 SQL 标准的同义词。 例如，`INT ARRAY` 是相当于`ARRAY<INT>`。
->
为了更接近 SQL 标准，也可以使用 `t ARRAY` 的写法表达，比如，`INT ARRAY` 等同于 `ARRAY<INT>`。
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -751,51 +729,45 @@ TIMESTAMP(p) WITHOUT TIME ZONE
DataTypes.TIMESTAMP(p)
```
-**Bridging to JVM Types**
+**JVM Types桥接**
-| Java Type | Input | Output | Remarks |
+| Java Type | 输入 | 输出 | 备注 |
|:-------------------------------------------|:-----:|:------:|:-------------------------|
-|`java.time.LocalDateTime` | X | X | *Default* |
+|`java.time.LocalDateTime` | X | X | *默认* |
|`java.sql.Timestamp` | X | X | |
-|`org.apache.flink.table.data.TimestampData` | X | X | Internal data structure. |
+|`org.apache.flink.table.data.TimestampData` | X | X | 内部数据结构。 |
{{< /tab >}}
{{< tab "Python" >}}
```python
DataTypes.TIMESTAMP(p)
```
-<span class="label label-danger">Attention</span> The `precision` specified in `DataTypes.TIMESTAMP(p)` must be `3` currently.
+<span class="label label-danger">请注意</span> 当前，`DataTypes.TIMESTAMP(p)` 中指定的 `precision` 必须为 `3`。
{{< /tab >}}
{{< /tabs >}}
-The type can be declared using `TIMESTAMP(p)` where `p` is the number of digits of fractional
-seconds (*precision*). `p` must have a value between `0` and `9` (both inclusive). If no precision
-is specified, `p` is equal to `6`.
+可以使用 `TIMESTAMP(p)` 声明该类型，其中 `p` 是小数秒的位数（*精度*）。 `p` 的取值范围为[`0`,`9`]。如果没有指定精度，p 等于 6。
-`TIMESTAMP(p) WITHOUT TIME ZONE` is a synonym for this type.
+`TIMESTAMP(p) WITHOUT TIME ZONE` 是这种类型的同义词。
#### `TIMESTAMP WITH TIME ZONE`
-Data type of a timestamp *with* time zone consisting of `year-month-day hour:minute:second[.fractional] zone`
-with up to nanosecond precision and values ranging from `0000-01-01 00:00:00.000000000 +14:59` to
-`9999-12-31 23:59:59.999999999 -14:59`.
+包含时区的时间戳的数据类型，格式为 `年-月-日 时：分：秒[.fractional]`，精度可达纳秒，取值范围为 `0000-01-01 00:00:00.000000000 +14:59` 至 `9999 -12-31 23:59:59.999999999 -14:59`。
{{< tabs "timestamps" >}}
{{< tab "SQL/Java/Scala" >}}
-Compared to the SQL standard, leap seconds (`23:59:60` and `23:59:61`) are not supported as the semantics
-are closer to `java.time.OffsetDateTime`.
+与 SQL 标准相比，不支持闰秒（`23:59:60` 和 `23:59:61`），其语义更接近`java.time.OffsetDateTime`。
{{< /tab >}}
{{< tab "Python" >}}
-Compared to the SQL standard, leap seconds (`23:59:60` and `23:59:61`) are not supported.
+与 SQL 标准相比，不支持闰秒（`23:59:60` 和 `23:59:61`）。
{{< /tab >}}
{{< /tabs >}}
-Compared to `TIMESTAMP_LTZ`, the time zone offset information is physically
-stored in every datum. It is used individually for every computation, visualization, or communication
-to external systems.
+与 `TIMESTAMP_LTZ` 相比，时区偏移信息物理存储在每个数据中。 它单独用于每次计算、可视化或与外部系统的通信。
Review Comment:
与 `TIMESTAMP_LTZ` 相比，时区偏移信息物理存储在每条数据中，便于每一次计算、数据显示、与外部系统进行通信。
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -686,55 +669,50 @@ TIME(p)
DataTypes.TIME(p)
```
-**Bridging to JVM Types**
+**JVM Types桥接**
-| Java Type | Input | Output | Remarks |
-|:---------------------|:-----:|:------:|:----------------------------------------------------|
-|`java.time.LocalTime` | X | X | *Default* |
-|`java.sql.Time` | X | X | |
-|`java.lang.Integer` | X | X | Describes the number of milliseconds of the day. |
-|`int` | X | (X) | Describes the number of milliseconds of the day.<br>Output only if type is not nullable. |
-|`java.lang.Long` | X | X | Describes the number of nanoseconds of the day. |
-|`long` | X | (X) | Describes the number of nanoseconds of the day.<br>Output only if type is not nullable. |
+| Java Type | 输入 | 输出 | 备注 |
+|:---------------------|:-----:|:------:|:----------------------------------------------------------------------------------------|
+|`java.time.LocalTime` | X | X | *默认* |
+|`java.sql.Time` | X | X | |
+|`java.lang.Integer` | X | X | 描述一天中的毫秒数。 |
+|`int` | X | (X) | 描述一天中的毫秒数。<br>仅当类型不可为空时才输出。 |
+|`java.lang.Long` | X | X | 描述一天中的纳秒数。 |
+|`long` | X | (X) | 描述一天中的纳秒数。<br>仅当类型不可为空时才输出。 |
{{< /tab >}}
{{< tab "Python" >}}
```python
DataTypes.TIME(p)
```
-<span class="label label-danger">Attention</span> The `precision` specified in `DataTypes.TIME(p)` must be `0` currently.
+<span class="label label-danger">请注意</span> 当前，`DataTypes.TIME(p)` 中指定的 `precision` 必须为 `0`。
{{< /tab >}}
{{< /tabs >}}
-The type can be declared using `TIME(p)` where `p` is the number of digits of fractional
-seconds (*precision*). `p` must have a value between `0` and `9` (both inclusive). If no
-precision is specified, `p` is equal to `0`.
+可以使用 `TIME(p)` 声明该类型，其中 `p` 是小数秒的位数（精度）。 p 的取值范围为[`0`,`9`]。 如果未指定精度，则 p 等于 0。
#### `TIMESTAMP`
-Data type of a timestamp *without* time zone consisting of `year-month-day hour:minute:second[.fractional]`
-with up to nanosecond precision and values ranging from `0000-01-01 00:00:00.000000000` to
-`9999-12-31 23:59:59.999999999`.
+有时区的时间类型，由 `年-月-日 小时:分钟:秒[.fractional]`组成，具有高达纳秒的精度，范围从`0000-01-01 00:00:00.000000000`到 `9999-12-31 23:59:59.999999999`。
{{< tabs "timestamps" >}}
{{< tab "SQL/Java/Scala" >}}
-Compared to the SQL standard, leap seconds (`23:59:60` and `23:59:61`) are not supported as
-the semantics are closer to `java.time.LocalDateTime`.
+与 SQL 标准相比，不支持闰秒（`23:59:60` 和 `23:59:61`）这种语义更接近`java.time.LocalDateTime`。
+
+不支持从和到 `BIGINT`（JVM `long` 类型）的转换，因为这将暗示时区。 但是，这种类型是无时区限制。 有关更多类似“java.time.Instant”的语义，请使用`TIMESTAMP_LTZ`。
Review Comment:
从和到?Is there something missing here? It doesn't feel very fluent and seems a little confusing.
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -657,22 +640,22 @@ DataTypes.DATE()
#### `TIME`
-Data type of a time *without* time zone consisting of `hour:minute:second[.fractional]` with
-up to nanosecond precision and values ranging from `00:00:00.000000000` to
-`23:59:59.999999999`.
+无时区的时间类型，包括 `小时:分钟:秒[.fractional]`，精度可达纳秒，取值范围为` 00:00:00.000000000` 到 `23:59:59.999999999`。
Review Comment:
Missing fractional?
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -898,33 +865,26 @@ DataTypes.TIMESTAMP_LTZ(p)
DataTypes.TIMESTAMP_WITH_LOCAL_TIME_ZONE(p)
```
-<span class="label label-danger">Attention</span> The `precision` specified in `DataTypes.TIMESTAMP_LTZ(p)` must be `3` currently.
+<span class="label label-danger">请注意</span> 当前，`DataTypes.TIMESTAMP_LTZ(p)` 中指定的 `precision` 必须为 `3`。
Review Comment:
precision -> 精度
--
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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] ChengkaiYang2022 commented on pull request #19964: [FLINK-27291][docs-zh] Translate the "List of Data Types" section of…
Posted by GitBox <gi...@apache.org>.
ChengkaiYang2022 commented on PR #19964:
URL: https://github.com/apache/flink/pull/19964#issuecomment-1164315959
> >
>
> translating '（both inclusive）' will catch the Chinese reader's attention more than just using '[' and ']' . I agree with that . catche the attention
Okay, Thanks. After you finish solving those typo problems, please ping me again.
--
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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] ChengkaiYang2022 commented on pull request #19964: [FLINK-27291][docs-zh] Translate the "List of Data Types" section of…
Posted by GitBox <gi...@apache.org>.
ChengkaiYang2022 commented on PR #19964:
URL: https://github.com/apache/flink/pull/19964#issuecomment-1233739560
No response from the @cason0126. Open another [PR](https://github.com/apache/flink/pull/20724) to continue the rest work.
--
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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] coder-zjh commented on pull request #19964: [FLINK-27291][docs-zh] Translate the "List of Data Types" section of…
Posted by GitBox <gi...@apache.org>.
coder-zjh commented on PR #19964:
URL: https://github.com/apache/flink/pull/19964#issuecomment-1221976073
Could I continue the job? ^^
--
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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] ChengkaiYang2022 commented on a diff in pull request #19964: [FLINK-27291][docs-zh] Translate the "List of Data Types" section of…
Posted by GitBox <gi...@apache.org>.
ChengkaiYang2022 commented on code in PR #19964:
URL: https://github.com/apache/flink/pull/19964#discussion_r901132913
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -142,56 +142,54 @@ val t: DataType = DataTypes.ARRAY(DataTypes.INT().notNull()).bridgedTo(classOf[A
API is extended. Users of predefined sources/sinks/functions do not need to define such hints. Hints within
a table program (e.g. `field.cast(TIMESTAMP(3).bridgedTo(Timestamp.class))`) are ignored.
-List of Data Types
+数据类型列表
------------------
-
-This section lists all pre-defined data types.
+这部分列举了所有预定义的数据类型。
{{< tabs "datatypesimport" >}}
{{< tab "Java/Scala" >}}
-For the JVM-based Table API those types are also available in `org.apache.flink.table.api.DataTypes`.
+Java/Scala Table API的数据类型详见： `org.apache.flink.table.api.DataTypes`.
{{< /tab >}}
{{< tab "Python" >}}
-For the Python Table API, those types are available in `pyflink.table.types.DataTypes`.
+Python Table API, 的数据类型详见： `pyflink.table.types.DataTypes`.
{{< /tab >}}
{{< /tabs >}}
-The default planner supports the following set of SQL types:
-
-| Data Type | Remarks for Data Type |
-|:-----------------|:---------------------------------------------------|
-| `CHAR` | |
-| `VARCHAR` | |
-| `STRING` | |
-| `BOOLEAN` | |
-| `BINARY` | |
-| `VARBINARY` | |
-| `BYTES` | |
-| `DECIMAL` | Supports fixed precision and scale. |
-| `TINYINT` | |
-| `SMALLINT` | |
-| `INTEGER` | |
-| `BIGINT` | |
-| `FLOAT` | |
-| `DOUBLE` | |
-| `DATE` | |
-| `TIME` | Supports only a precision of `0`. |
-| `TIMESTAMP` | |
-| `TIMESTAMP_LTZ` | |
-| `INTERVAL` | Supports only interval of `MONTH` and `SECOND(3)`. |
-| `ARRAY` | |
-| `MULTISET` | |
-| `MAP` | |
-| `ROW` | |
-| `RAW` | |
-| Structured types | Only exposed in user-defined functions yet. |
-
-### Character Strings
+默认 `Planner` 支持下列SQL数据类型：
+
+| 数据类型 | 备注 |
+|:-----------------|:---------------------|
+| `CHAR` | |
+| `VARCHAR` | |
+| `STRING` | |
+| `BOOLEAN` | |
+| `BINARY` | |
+| `VARBINARY` | |
+| `BYTES` | |
+| `DECIMAL` | 支持固定精度和比例 |
Review Comment:
Missing '。'？
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -205,32 +203,29 @@ CHAR(n)
DataTypes.CHAR(n)
```
-**Bridging to JVM Types**
+**JVM Types桥接**
-| Java Type | Input | Output | Remarks |
-|:----------------------------------------|:-----:|:------:|:-------------------------|
-|`java.lang.String` | X | X | *Default* |
-|`byte[]` | X | X | Assumes UTF-8 encoding. |
-|`org.apache.flink.table.data.StringData` | X | X | Internal data structure. |
+| Java Type | 输入 | 输入 | 备注 |
+|:-----------------------------------------|:-----:|:------:|:------------|
+| `java.lang.String` | X | X | *默认* |
+| `byte[]` | X | X | 假定 UTF-8 编码 |
+| `org.apache.flink.table.data.StringData` | X | X | 内部数据结构 |
{{< /tab >}}
{{< tab "Python" >}}
```python
-Not supported.
+Not supported.。
Review Comment:
Please the using Chinese character here '。' instead of '.'
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -386,36 +377,34 @@ NUMERIC(p, s)
DataTypes.DECIMAL(p, s)
```
-**Bridging to JVM Types**
+**JVM Types桥接**
-| Java Type | Input | Output | Remarks |
+| Java Type | 输入 | 输出 | 备注 |
|:-----------------------------------------|:-----:|:------:|:-------------------------|
-|`java.math.BigDecimal` | X | X | *Default* |
-|`org.apache.flink.table.data.DecimalData` | X | X | Internal data structure. |
+|`java.math.BigDecimal` | X | X | *默认* |
+|`org.apache.flink.table.data.DecimalData` | X | X | 内部数据结构。 |
{{< /tab >}}
{{< tab "Python" >}}
```python
DataTypes.DECIMAL(p, s)
```
-<span class="label label-danger">Attention</span> The `precision` and `scale` specified in `DataTypes.DECIMAL(p, s)` must be `38` and `18` separately currently.
+<span class="label label-danger">请注意</span> 当前， `DataTypes.DECIMAL(p, s)`中指定的`precision`和`scale`当前必须分别为`38`和`18`。
Review Comment:
Please be careful about the space problem.
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -142,56 +142,54 @@ val t: DataType = DataTypes.ARRAY(DataTypes.INT().notNull()).bridgedTo(classOf[A
API is extended. Users of predefined sources/sinks/functions do not need to define such hints. Hints within
a table program (e.g. `field.cast(TIMESTAMP(3).bridgedTo(Timestamp.class))`) are ignored.
-List of Data Types
+数据类型列表
------------------
-
-This section lists all pre-defined data types.
+这部分列举了所有预定义的数据类型。
{{< tabs "datatypesimport" >}}
{{< tab "Java/Scala" >}}
-For the JVM-based Table API those types are also available in `org.apache.flink.table.api.DataTypes`.
+Java/Scala Table API的数据类型详见： `org.apache.flink.table.api.DataTypes`.
{{< /tab >}}
{{< tab "Python" >}}
-For the Python Table API, those types are available in `pyflink.table.types.DataTypes`.
+Python Table API, 的数据类型详见： `pyflink.table.types.DataTypes`.
{{< /tab >}}
{{< /tabs >}}
-The default planner supports the following set of SQL types:
-
-| Data Type | Remarks for Data Type |
-|:-----------------|:---------------------------------------------------|
-| `CHAR` | |
-| `VARCHAR` | |
-| `STRING` | |
-| `BOOLEAN` | |
-| `BINARY` | |
-| `VARBINARY` | |
-| `BYTES` | |
-| `DECIMAL` | Supports fixed precision and scale. |
-| `TINYINT` | |
-| `SMALLINT` | |
-| `INTEGER` | |
-| `BIGINT` | |
-| `FLOAT` | |
-| `DOUBLE` | |
-| `DATE` | |
-| `TIME` | Supports only a precision of `0`. |
-| `TIMESTAMP` | |
-| `TIMESTAMP_LTZ` | |
-| `INTERVAL` | Supports only interval of `MONTH` and `SECOND(3)`. |
-| `ARRAY` | |
-| `MULTISET` | |
-| `MAP` | |
-| `ROW` | |
-| `RAW` | |
-| Structured types | Only exposed in user-defined functions yet. |
-
-### Character Strings
+默认 `Planner` 支持下列SQL数据类型：
+
+| 数据类型 | 备注 |
+|:-----------------|:---------------------|
+| `CHAR` | |
+| `VARCHAR` | |
+| `STRING` | |
+| `BOOLEAN` | |
+| `BINARY` | |
+| `VARBINARY` | |
+| `BYTES` | |
+| `DECIMAL` | 支持固定精度和比例 |
+| `TINYINT` | |
+| `SMALLINT` | |
+| `INTEGER` | |
+| `BIGINT` | |
+| `FLOAT` | |
+| `DOUBLE` | |
+| `DATE` | |
+| `TIME` | 仅支到0.的精度 |
+| `TIMESTAMP` | |
+| `TIMESTAMP_LTZ` | |
+| `INTERVAL` | 仅支持MONTH 到 SECOND(3） |
Review Comment:
Please add space between English characters and Chinese characters. And please check this kind of problem in the rest section.
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -307,15 +300,14 @@ Not supported.
{{< /tab >}}
{{< /tabs >}}
-The type can be declared using `BINARY(n)` where `n` is the number of bytes. `n` must have a value
-between `1` and `2,147,483,647` (both inclusive). If no length is specified, `n` is equal to `1`.
+可以使用 `BINARY(n)` 声明该类型，其中 `n` 表示字节数。 `n` 的取值范围为 [`1` , `2,147,483,647` ] 如果没有指定 `n` 的值， n 等于 1。
#### `VARBINARY` / `BYTES`
-Data type of a variable-length binary string (=a sequence of bytes).
+可变长度的二进制字符串的数据类型（可以理解为是一种字节序列）
Review Comment:
Missing '。'
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -142,56 +142,54 @@ val t: DataType = DataTypes.ARRAY(DataTypes.INT().notNull()).bridgedTo(classOf[A
API is extended. Users of predefined sources/sinks/functions do not need to define such hints. Hints within
a table program (e.g. `field.cast(TIMESTAMP(3).bridgedTo(Timestamp.class))`) are ignored.
-List of Data Types
+数据类型列表
------------------
-
-This section lists all pre-defined data types.
+这部分列举了所有预定义的数据类型。
{{< tabs "datatypesimport" >}}
{{< tab "Java/Scala" >}}
-For the JVM-based Table API those types are also available in `org.apache.flink.table.api.DataTypes`.
+Java/Scala Table API的数据类型详见： `org.apache.flink.table.api.DataTypes`.
{{< /tab >}}
{{< tab "Python" >}}
-For the Python Table API, those types are available in `pyflink.table.types.DataTypes`.
+Python Table API, 的数据类型详见： `pyflink.table.types.DataTypes`.
{{< /tab >}}
{{< /tabs >}}
-The default planner supports the following set of SQL types:
-
-| Data Type | Remarks for Data Type |
-|:-----------------|:---------------------------------------------------|
-| `CHAR` | |
-| `VARCHAR` | |
-| `STRING` | |
-| `BOOLEAN` | |
-| `BINARY` | |
-| `VARBINARY` | |
-| `BYTES` | |
-| `DECIMAL` | Supports fixed precision and scale. |
-| `TINYINT` | |
-| `SMALLINT` | |
-| `INTEGER` | |
-| `BIGINT` | |
-| `FLOAT` | |
-| `DOUBLE` | |
-| `DATE` | |
-| `TIME` | Supports only a precision of `0`. |
-| `TIMESTAMP` | |
-| `TIMESTAMP_LTZ` | |
-| `INTERVAL` | Supports only interval of `MONTH` and `SECOND(3)`. |
-| `ARRAY` | |
-| `MULTISET` | |
-| `MAP` | |
-| `ROW` | |
-| `RAW` | |
-| Structured types | Only exposed in user-defined functions yet. |
-
-### Character Strings
+默认 `Planner` 支持下列SQL数据类型：
Review Comment:
Please add space between [English charater and Chinese charate](https://cwiki.apache.org/confluence/display/FLINK/Flink+Translation+Specifications)
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -142,56 +142,54 @@ val t: DataType = DataTypes.ARRAY(DataTypes.INT().notNull()).bridgedTo(classOf[A
API is extended. Users of predefined sources/sinks/functions do not need to define such hints. Hints within
a table program (e.g. `field.cast(TIMESTAMP(3).bridgedTo(Timestamp.class))`) are ignored.
-List of Data Types
+数据类型列表
------------------
-
-This section lists all pre-defined data types.
+这部分列举了所有预定义的数据类型。
{{< tabs "datatypesimport" >}}
{{< tab "Java/Scala" >}}
-For the JVM-based Table API those types are also available in `org.apache.flink.table.api.DataTypes`.
+Java/Scala Table API的数据类型详见： `org.apache.flink.table.api.DataTypes`.
{{< /tab >}}
{{< tab "Python" >}}
-For the Python Table API, those types are available in `pyflink.table.types.DataTypes`.
+Python Table API, 的数据类型详见： `pyflink.table.types.DataTypes`.
{{< /tab >}}
{{< /tabs >}}
-The default planner supports the following set of SQL types:
-
-| Data Type | Remarks for Data Type |
-|:-----------------|:---------------------------------------------------|
-| `CHAR` | |
-| `VARCHAR` | |
-| `STRING` | |
-| `BOOLEAN` | |
-| `BINARY` | |
-| `VARBINARY` | |
-| `BYTES` | |
-| `DECIMAL` | Supports fixed precision and scale. |
-| `TINYINT` | |
-| `SMALLINT` | |
-| `INTEGER` | |
-| `BIGINT` | |
-| `FLOAT` | |
-| `DOUBLE` | |
-| `DATE` | |
-| `TIME` | Supports only a precision of `0`. |
-| `TIMESTAMP` | |
-| `TIMESTAMP_LTZ` | |
-| `INTERVAL` | Supports only interval of `MONTH` and `SECOND(3)`. |
-| `ARRAY` | |
-| `MULTISET` | |
-| `MAP` | |
-| `ROW` | |
-| `RAW` | |
-| Structured types | Only exposed in user-defined functions yet. |
-
-### Character Strings
+默认 `Planner` 支持下列SQL数据类型：
+
+| 数据类型 | 备注 |
+|:-----------------|:---------------------|
+| `CHAR` | |
+| `VARCHAR` | |
+| `STRING` | |
+| `BOOLEAN` | |
+| `BINARY` | |
+| `VARBINARY` | |
+| `BYTES` | |
+| `DECIMAL` | 支持固定精度和比例 |
+| `TINYINT` | |
+| `SMALLINT` | |
+| `INTEGER` | |
+| `BIGINT` | |
+| `FLOAT` | |
+| `DOUBLE` | |
+| `DATE` | |
+| `TIME` | 仅支到0.的精度 |
Review Comment:
Missing '。'？支持 instead of 支?
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -264,22 +259,20 @@ DataTypes.VARCHAR(n)
DataTypes.STRING()
```
-<span class="label label-danger">Attention</span> The specified maximum number of code points `n` in `DataTypes.VARCHAR(n)` must be `2,147,483,647` currently.
+<span class="label label-danger">请注意</span> 目前，`DataTypes.VARCHAR(n)` 中指定的最大指 `n` 当前必须为 `2,147,483,647`。
Review Comment:
值 instead of 指
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -638,14 +621,14 @@ DATE
DataTypes.DATE()
```
-**Bridging to JVM Types**
+**JVM Types桥接**
-| Java Type | Input | Output | Remarks |
+| Java Type | 输入 | 输出 | 备注 |
|:---------------------|:-----:|:------:|:---------------------------------------------|
-|`java.time.LocalDate` | X | X | *Default* |
+|`java.time.LocalDate` | X | X | *默认* |
|`java.sql.Date` | X | X | |
-|`java.lang.Integer` | X | X | Describes the number of days since epoch. |
-|`int` | X | (X) | Describes the number of days since epoch.<br>Output only if type is not nullable. |
+|`java.lang.Integer` | X | X | 描述自纪元以来的天数。 |
Review Comment:
It feels like '纪元' is not a very common term in technical documentation, maybe it should be expressed in another term?
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -307,15 +300,14 @@ Not supported.
{{< /tab >}}
{{< /tabs >}}
-The type can be declared using `BINARY(n)` where `n` is the number of bytes. `n` must have a value
-between `1` and `2,147,483,647` (both inclusive). If no length is specified, `n` is equal to `1`.
+可以使用 `BINARY(n)` 声明该类型，其中 `n` 表示字节数。 `n` 的取值范围为 [`1` , `2,147,483,647` ] 如果没有指定 `n` 的值， n 等于 1。
Review Comment:
Missing comma before 如果没有指定 `n` 的值?
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -264,22 +259,20 @@ DataTypes.VARCHAR(n)
DataTypes.STRING()
```
-<span class="label label-danger">Attention</span> The specified maximum number of code points `n` in `DataTypes.VARCHAR(n)` must be `2,147,483,647` currently.
+<span class="label label-danger">请注意</span> 目前，`DataTypes.VARCHAR(n)` 中指定的最大指 `n` 当前必须为 `2,147,483,647`。
{{< /tab >}}
{{< /tabs >}}
-The type can be declared using `VARCHAR(n)` where `n` is the maximum number of code points. `n` must have a value
-between `1` and `2,147,483,647` (both inclusive). If no length is specified, `n` is equal to `1`.
+可以使用 `VARCHAR(n)` 声明该类型，其中 `n` 表示其最大值。`n` 的取值范围为[ `1` , `2,147,483,647` ] ，如果没有指定 `n` 的值，n 等于 1。
Review Comment:
How about translating (both inclusive) instead of using '[' and ']' characters to let this line more specific?
##########
docs/content.zh/docs/dev/table/types.md:
##########
@@ -614,18 +599,16 @@ DataTypes.DOUBLE()
{{< /tab >}}
{{< /tabs >}}
-`DOUBLE PRECISION` is a synonym for this type.
+`DOUBLE PRECISION` 是这种类型的同义词。
-### Date and Time
+### 日期和时间
#### `DATE`
-Data type of a date consisting of `year-month-day` with values ranging from `0000-01-01`
-to `9999-12-31`.
-
-Compared to the SQL standard, the range starts at year `0000`.
+日期的数据类型，由 `年-月-日` 组成，取值范围为 `0000-01-01` 到 `9999-12-31` 。
Review Comment:
When we translate from A to B, maybe we should only use ' A 到 B' or only use 'A ~ B'?
It's better to unify the translation method.
--
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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] cason0126 commented on pull request #19964: [FLINK-27291][docs-zh] Translate the "List of Data Types" section of…
Posted by GitBox <gi...@apache.org>.
cason0126 commented on PR #19964:
URL: https://github.com/apache/flink/pull/19964#issuecomment-1159896445
@ChengkaiYang2022 Thanks for correcting. I will fix them ;
There is one part I am confusing about : using (both inclusive) instead of using '[' and ']' 。 I think using `[` and`] is the same way as （both inclusive） while this way can use fewer characters 。
Is it this way that creates ambiguity ?
--
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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] ChengkaiYang2022 commented on pull request #19964: [FLINK-27291][docs-zh] Translate the "List of Data Types" section of…
Posted by GitBox <gi...@apache.org>.
ChengkaiYang2022 commented on PR #19964:
URL: https://github.com/apache/flink/pull/19964#issuecomment-1192245935
Hi, @cason0126 Any update for your end on this?
--
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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] flinkbot commented on pull request #19964: [FLINK-27291][docs-zh] Translate the "List of Data Types" section of…
Posted by GitBox <gi...@apache.org>.
flinkbot commented on PR #19964:
URL: https://github.com/apache/flink/pull/19964#issuecomment-1156223148
<!--
Meta data
{
"version" : 1,
"metaDataEntries" : [ {
"hash" : "c589aa821f1dced9057828193a06c183b1b3f588",
"status" : "UNKNOWN",
"url" : "TBD",
"triggerID" : "c589aa821f1dced9057828193a06c183b1b3f588",
"triggerType" : "PUSH"
} ]
}-->
## CI report:
* c589aa821f1dced9057828193a06c183b1b3f588 UNKNOWN
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run azure` re-run the last Azure build
</details>
--
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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] ChengkaiYang2022 commented on pull request #19964: [FLINK-27291][docs-zh] Translate the "List of Data Types" section of…
Posted by GitBox <gi...@apache.org>.
ChengkaiYang2022 commented on PR #19964:
URL: https://github.com/apache/flink/pull/19964#issuecomment-1159768087
@cason0126 Thanks for your contribution!
And could you share the screen snapshot about the doc you modified? https://github.com/apache/flink/pull/19498#issuecomment-1113981445
--
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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [flink] ChengkaiYang2022 commented on pull request #19964: [FLINK-27291][docs-zh] Translate the "List of Data Types" section of…
Posted by GitBox <gi...@apache.org>.
ChengkaiYang2022 commented on PR #19964:
URL: https://github.com/apache/flink/pull/19964#issuecomment-1161860720
> @ChengkaiYang2022 Thanks for correcting. I will fix them ; There is one part I am confusing about : using (both inclusive) instead of using '[' and ']' 。 I think using `[` and`] is the same way as （both inclusive） while this way can use fewer characters 。 Is it this way that creates ambiguity ?
Using '[' and ']' is a way that use fewer charaters, while I think translate '（both inclusive）' in to Chinese could be more specific since most Chinese readers are more familiar with the TEXT '开闭区间’ instead of the CHARATERS '[' or ']'.
--
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.
To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org