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 2020/01/01 17:37:34 UTC
[GitHub] [flink] ousheobin opened a new pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
ousheobin opened a new pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738
<!--
*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 Travis CI to do that following [this guide](https://flink.apache.org/contributing/contribute-code.html#open-a-pull-request).
- 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
Document Translation.
## Brief change log
- Translated the SQL section of Table API documents into Chinese
## Verifying this change
*(Please pick either of the following options)*
This change is a trivial rework / code cleanup without any test coverage.
*(or)*
This change is already covered by existing tests, such as *(please describe tests)*.
*(or)*
This change added tests and can be verified as follows:
*(example:)*
- *Added integration tests for end-to-end deployment with large payloads (100MB)*
- *Extended integration test for recovery after master (JobManager) failure*
- *Added test that validates that TaskInfo is transferred only once across recoveries*
- *Manually verified the change by running a 4 node cluser with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.*
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (yes / **no**)
- The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**)
- The serializers: (yes / **no** / don't know)
- The runtime per-record code paths (performance sensitive): (yes / **no** / don't know)
- Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know)
- The S3 file system connector: (yes / **no** / don't know)
## Documentation
- Does this pull request introduce a new feature? (yes / **no**)
- If yes, how is the feature documented? (not applicable / docs / JavaDocs / **not documented**)
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362368088
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -587,61 +587,61 @@ WHERE o.id = s.orderId AND
o.ordertime BETWEEN s.shiptime - INTERVAL '4' HOUR AND s.shiptime
{% endhighlight %}
-The example above will join all orders with their corresponding shipments if the order was shipped four hours after the order was received.
+以上示例中，所有在收到后四小时内发货的 order 会与他们相关的 shipment 进行 join。
</td>
</tr>
<tr>
- <td>
+ <td>
<strong>Expanding arrays into a relation</strong><br>
- <span class="label label-primary">Batch</span> <span class="label label-primary">Streaming</span>
+ <span class="label label-primary">批处理</span> <span class="label label-primary">流处理</span>
</td>
- <td>
- <p>Unnesting WITH ORDINALITY is not supported yet.</p>
+ <td>
+ <p>目前尚未支持非嵌套的 WITH ORDINALITY 。</p>
{% highlight sql %}
SELECT users, tag
FROM Orders CROSS JOIN UNNEST(tags) AS t (tag)
{% endhighlight %}
</td>
</tr>
<tr>
- <td>
- <strong>Join with Table Function (UDTF)</strong><br>
- <span class="label label-primary">Batch</span> <span class="label label-primary">Streaming</span>
+ <td>
+ <strong>Join 表函数 (UDTF)</strong><br>
+ <span class="label label-primary">批处理</span> <span class="label label-primary">流处理</span>
</td>
- <td>
- <p>Joins a table with the results of a table function. Each row of the left (outer) table is joined with all rows produced by the corresponding call of the table function.</p>
- <p>User-defined table functions (UDTFs) must be registered before. See the <a href="{{ site.baseurl }}/dev/table/functions/udfs.html">UDF documentation</a> for details on how to specify and register UDTFs. </p>
+ <td>
+ <p>将表与表函数的结果进行 join 操作。左表（outer）中的每一行将会与调用表函数所产生的所有结果中相关联行进行 join 。</p>
+ <p>用户自定义表函数（ User-defined table functions，UDTFs ） 在执行前必须先注册。请参考 <a href="{{ site.baseurl }}/zh/dev/table/functions/udfs.html">UDF 文档</a> 以获取更多关于指定和注册UDF的信息 </p>
<p><b>Inner Join</b></p>
- <p>A row of the left (outer) table is dropped, if its table function call returns an empty result.</p>
+ <p>若表函数返回了空结果，左表（outer）的行将会被删除。</p>
{% highlight sql %}
SELECT users, tag
FROM Orders, LATERAL TABLE(unnest_udtf(tags)) t AS tag
{% endhighlight %}
<p><b>Left Outer Join</b></p>
- <p>If a table function call returns an empty result, the corresponding outer row is preserved and the result padded with null values.</p>
+ <p>若表函数返回了空结果，将会保留相对应的外部行并用空值填充结果。</p>
{% highlight sql %}
SELECT users, tag
FROM Orders LEFT JOIN LATERAL TABLE(unnest_udtf(tags)) t AS tag ON TRUE
{% endhighlight %}
- <p><b>Note:</b> Currently, only literal <code>TRUE</code> is supported as predicate for a left outer join against a lateral table.</p>
+ <p><b>注意：</b> 当前仅支持文本常量 <code>TRUE</code> 作为针对横向表的左外部联接的谓词。</p>
</td>
</tr>
<tr>
<td>
- <strong>Join with Temporal Table Function</strong><br>
- <span class="label label-primary">Streaming</span>
+ <strong>Join Temporal Tables 函数</strong><br>
+ <span class="label label-primary">流处理</span>
</td>
<td>
- <p><a href="{{ site.baseurl }}/dev/table/streaming/temporal_tables.html">Temporal tables</a> are tables that track changes over time.</p>
- <p>A <a href="{{ site.baseurl }}/dev/table/streaming/temporal_tables.html#temporal-table-functions">Temporal table function</a> provides access to the state of a temporal table at a specific point in time.
- The syntax to join a table with a temporal table function is the same as in <i>Join with Table Function</i>.</p>
+ <p><a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html">Temporal Tables</a> 是跟随时间变化而变化的表。</p>
+ <p><a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html#temporal-table-functions"> Temporal Tables 函数（ Temporal table function ）</a> 提供访问 Temporal Tables 在某一时间点的状态的能力。
Review comment:
```suggestion
<p><a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html#temporal-table-functions"> Temporal Table Function</a> 提供访问 Temporal Tables 在某一时间点的状态的能力。
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362364060
##########
File path: docs/dev/table/sql/create.zh.md
##########
@@ -141,44 +141,44 @@ CREATE TABLE [catalog_name.][db_name.]table_name
{% endhighlight %}
-Creates a table with the given name. If a table with the same name already exists in the catalog, an exception is thrown.
+根据给定的表属性创建表。若数据库中已存在同名表会抛出异常。
**COMPUTED COLUMN**
-A computed column is a virtual column that is generated using the syntax "`column_name AS computed_column_expression`". It is generated from a non-query expression that uses other columns in the same table and is not physically stored within the table. For example, a computed column could be defined as `cost AS price * quantity`. The expression may contain any combination of physical column, constant, function, or variable. The expression cannot contain a subquery.
+计算列是一个使用 “`column_name AS computed_column_expression`” 语法生成的虚拟列。它由使用同一表中其他列的非查询表达式生成，并且不会在表中进行物理存储。例如，一个计算列可以使用 `cost AS price * quantity` 进行定义，这个表达式可以包含物理列、常量、函数或变量的任意组合，但这个表达式不能存在任何子查询。
-Computed columns are commonly used in Flink for defining [time attributes]({{ site.baseurl}}/dev/table/streaming/time_attributes.html) in CREATE TABLE statements.
-A [processing time attribute]({{ site.baseurl}}/dev/table/streaming/time_attributes.html#processing-time) can be defined easily via `proc AS PROCTIME()` using the system `PROCTIME()` function.
-On the other hand, computed column can be used to derive event time column because an event time column may need to be derived from existing fields, e.g. the original field is not `TIMESTAMP(3)` type or is nested in a JSON string.
+在 Flink 中计算列一般用于为 CREATE TABLE 语句定义 [时间属性]({{ site.baseurl}}/zh/dev/table/streaming/time_attributes.html)。
+[处理时间属性]({{ site.baseurl}}/zh/dev/table/streaming/time_attributes.html#processing-time) 可以简单地通过使用了系统函数 `PROCTIME()` 的 `proc AS PROCTIME()` 语句进行定义。
+另一方面，由于事件时间列可能需要从现有的字段中获得，因此计算列可用于获得事件时间列。例如，原始字段的类型不是 `TIMESTAMP(3)` 或嵌套在 JSON 字符串中。
-Notes:
+注意：
-- A computed column defined on a source table is computed after reading from the source, it can be used in the following SELECT query statements.
-- A computed column cannot be the target of an INSERT statement. In INSERT statements, the schema of SELECT clause should match the schema of the target table without computed columns.
+- 定义在一个数据源表（ source table ）上的计算列会在从数据源读取数据后被计算，它们可以在 SELECT 查询语句后使用。
Review comment:
```suggestion
- 定义在一个数据源表（ source table ）上的计算列会在从数据源读取数据后被计算，它们可以在 SELECT 查询语句中使用。
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362367671
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -1116,68 +1111,68 @@ The start and end timestamps of group windows as well as time attributes can be
<code>HOP_START(time_attr, interval, interval)</code><br/>
<code>SESSION_START(time_attr, interval)</code><br/>
</td>
- <td><p>Returns the timestamp of the inclusive lower bound of the corresponding tumbling, hopping, or session window.</p></td>
+ <td><p>返回相对应的滚动，滑动和会话窗口范围内的下界时间戳。</p></td>
</tr>
<tr>
<td>
<code>TUMBLE_END(time_attr, interval)</code><br/>
<code>HOP_END(time_attr, interval, interval)</code><br/>
<code>SESSION_END(time_attr, interval)</code><br/>
</td>
- <td><p>Returns the timestamp of the <i>exclusive</i> upper bound of the corresponding tumbling, hopping, or session window.</p>
- <p><b>Note:</b> The exclusive upper bound timestamp <i>cannot</i> be used as a <a href="{{ site.baseurl }}/dev/table/streaming/time_attributes.html">rowtime attribute</a> in subsequent time-based operations, such as <a href="#joins">time-windowed joins</a> and <a href="#aggregations">group window or over window aggregations</a>.</p></td>
+ <td><p>返回相对应的滚动，滑动和会话窗口<i>范围以外</i>的上界时间戳。</p>
+ <p><b>注意：</b> 范围以外的上界时间戳<i>不可以</i> 在随后基于时间的操作中，作为 <a href="{{ site.baseurl }}/zh/dev/table/streaming/time_attributes.html">行时间属性</a> 使用，比如 <a href="#joins">基于时间窗口的 join </a> 以及 <a href="#aggregations">分组窗口或分组窗口上的聚合</a>。</p></td>
</tr>
<tr>
<td>
<code>TUMBLE_ROWTIME(time_attr, interval)</code><br/>
<code>HOP_ROWTIME(time_attr, interval, interval)</code><br/>
<code>SESSION_ROWTIME(time_attr, interval)</code><br/>
</td>
- <td><p>Returns the timestamp of the <i>inclusive</i> upper bound of the corresponding tumbling, hopping, or session window.</p>
- <p>The resulting attribute is a <a href="{{ site.baseurl }}/dev/table/streaming/time_attributes.html">rowtime attribute</a> that can be used in subsequent time-based operations such as <a href="#joins">time-windowed joins</a> and <a href="#aggregations">group window or over window aggregations</a>.</p></td>
+ <td><p>返回相对应的滚动，滑动和会话窗口<i>范围以内</i>的上界时间戳。</p>
Review comment:
```suggestion
<td><p>返回相对应的滚动、滑动和会话窗口<i>范围以内</i>的上界时间戳。</p>
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362363555
##########
File path: docs/dev/table/sql/alter.zh.md
##########
@@ -110,28 +110,28 @@ NewOrders
</div>
</div>
-## ALTER TABLE
+## 修改表
-* Rename Table
+* 重命名表
{% highlight sql %}
ALTER TABLE [catalog_name.][db_name.]table_name RENAME TO new_table_name
{% endhighlight %}
-Rename the given table name to another new table name.
+把原有的表名更改为新的表名。
-* Set or Alter Table Properties
+* 设置或修改表属性
{% highlight sql %}
ALTER TABLE [catalog_name.][db_name.]table_name SET (key1=val1, key2=val2, ...)
{% endhighlight %}
-Set one or more properties in the specified table. If a particular property is already set in the table, override the old value with the new one.
+为指定的表设置一个或多个属性。若个别属性已经存在于表中，则使用新的值覆盖旧的值。
-## ALTER DATABASE
+## 修改数据库
Review comment:
Please revert. This refers to the `ALTER DATABSE` statement which shouldn't be translated.
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362367954
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -587,61 +587,61 @@ WHERE o.id = s.orderId AND
o.ordertime BETWEEN s.shiptime - INTERVAL '4' HOUR AND s.shiptime
{% endhighlight %}
-The example above will join all orders with their corresponding shipments if the order was shipped four hours after the order was received.
+以上示例中，所有在收到后四小时内发货的 order 会与他们相关的 shipment 进行 join。
</td>
</tr>
<tr>
- <td>
+ <td>
<strong>Expanding arrays into a relation</strong><br>
- <span class="label label-primary">Batch</span> <span class="label label-primary">Streaming</span>
+ <span class="label label-primary">批处理</span> <span class="label label-primary">流处理</span>
</td>
- <td>
- <p>Unnesting WITH ORDINALITY is not supported yet.</p>
+ <td>
+ <p>目前尚未支持非嵌套的 WITH ORDINALITY 。</p>
{% highlight sql %}
SELECT users, tag
FROM Orders CROSS JOIN UNNEST(tags) AS t (tag)
{% endhighlight %}
</td>
</tr>
<tr>
- <td>
- <strong>Join with Table Function (UDTF)</strong><br>
- <span class="label label-primary">Batch</span> <span class="label label-primary">Streaming</span>
+ <td>
+ <strong>Join 表函数 (UDTF)</strong><br>
+ <span class="label label-primary">批处理</span> <span class="label label-primary">流处理</span>
</td>
- <td>
- <p>Joins a table with the results of a table function. Each row of the left (outer) table is joined with all rows produced by the corresponding call of the table function.</p>
- <p>User-defined table functions (UDTFs) must be registered before. See the <a href="{{ site.baseurl }}/dev/table/functions/udfs.html">UDF documentation</a> for details on how to specify and register UDTFs. </p>
+ <td>
+ <p>将表与表函数的结果进行 join 操作。左表（outer）中的每一行将会与调用表函数所产生的所有结果中相关联行进行 join 。</p>
+ <p>用户自定义表函数（ User-defined table functions，UDTFs ） 在执行前必须先注册。请参考 <a href="{{ site.baseurl }}/zh/dev/table/functions/udfs.html">UDF 文档</a> 以获取更多关于指定和注册UDF的信息 </p>
<p><b>Inner Join</b></p>
- <p>A row of the left (outer) table is dropped, if its table function call returns an empty result.</p>
+ <p>若表函数返回了空结果，左表（outer）的行将会被删除。</p>
{% highlight sql %}
SELECT users, tag
FROM Orders, LATERAL TABLE(unnest_udtf(tags)) t AS tag
{% endhighlight %}
<p><b>Left Outer Join</b></p>
- <p>If a table function call returns an empty result, the corresponding outer row is preserved and the result padded with null values.</p>
+ <p>若表函数返回了空结果，将会保留相对应的外部行并用空值填充结果。</p>
{% highlight sql %}
SELECT users, tag
FROM Orders LEFT JOIN LATERAL TABLE(unnest_udtf(tags)) t AS tag ON TRUE
{% endhighlight %}
- <p><b>Note:</b> Currently, only literal <code>TRUE</code> is supported as predicate for a left outer join against a lateral table.</p>
+ <p><b>注意：</b> 当前仅支持文本常量 <code>TRUE</code> 作为针对横向表的左外部联接的谓词。</p>
</td>
</tr>
<tr>
<td>
- <strong>Join with Temporal Table Function</strong><br>
- <span class="label label-primary">Streaming</span>
+ <strong>Join Temporal Tables 函数</strong><br>
Review comment:
```suggestion
<strong>Join Temporal Table Function</strong><br>
```
这段还是不翻译吧，描述中的也对应修改一下。
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362367223
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -925,26 +923,26 @@ val result1 = tableEnv.sqlQuery(
</div>
</div>
-#### No Ranking Output Optimization
+#### 不进行排序输出的优化
Review comment:
```suggestion
#### 无排名输出优化
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362366959
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -651,20 +651,20 @@ FROM
WHERE
r_currency = o_currency
{% endhighlight %}
- <p>For more information please check the more detailed <a href="{{ site.baseurl }}/dev/table/streaming/temporal_tables.html">temporal tables concept description</a>.</p>
+ <p>请查看 <a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html"> Temporal Tables 概念描述</a> 以了解详细信息。</p>
</td>
</tr>
<tr>
<td>
- <strong>Join with Temporal Table</strong><br>
- <span class="label label-primary">Batch</span> <span class="label label-primary">Streaming</span>
+ <strong>Join Temporal Tables </strong><br>
+ <span class="label label-primary">批处理</span> <span class="label label-primary">流处理</span>
</td>
<td>
- <p><a href="{{ site.baseurl }}/dev/table/streaming/temporal_tables.html">Temporal Tables</a> are tables that track changes over time.
- A <a href="{{ site.baseurl }}/dev/table/streaming/temporal_tables.html#temporal-table">Temporal Table</a> provides access to the versions of a temporal table at a specific point in time.</p>
+ <p><a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html">Temporal Tables</a> 是随时间变化而变化的表。
+ <a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html#temporal-table">Temporal Table</a> 提供访问指定时间点的 temporal table 版本的功能。</p>
- <p>Only inner and left joins with processing-time temporal tables are supported.</p>
- <p>The following example assumes that <strong>LatestRates</strong> is a <a href="{{ site.baseurl }}/dev/table/streaming/temporal_tables.html#temporal-table">Temporal Table</a> which is materialized with the latest rate.</p>
+ <p>仅支持带有处理时间的 temporal tables 的 inner 和 left join。</p>
+ <p>下述示例中，假设 <strong>LatestRates</strong> 是一个根据最新的 rates 实现的 <a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html#temporal-table">Temporal Table</a> 。</p>
Review comment:
```suggestion
<p>下述示例中，假设 <strong>LatestRates</strong> 是一个根据最新的 rates 物化的 <a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html#temporal-table">Temporal Table</a> 。</p>
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362366667
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -587,61 +587,61 @@ WHERE o.id = s.orderId AND
o.ordertime BETWEEN s.shiptime - INTERVAL '4' HOUR AND s.shiptime
{% endhighlight %}
-The example above will join all orders with their corresponding shipments if the order was shipped four hours after the order was received.
+以上示例中，所有在收到后四小时内发货的 order 会与他们相关的 shipment 进行 join。
</td>
</tr>
<tr>
- <td>
+ <td>
<strong>Expanding arrays into a relation</strong><br>
- <span class="label label-primary">Batch</span> <span class="label label-primary">Streaming</span>
+ <span class="label label-primary">批处理</span> <span class="label label-primary">流处理</span>
</td>
- <td>
- <p>Unnesting WITH ORDINALITY is not supported yet.</p>
+ <td>
+ <p>目前尚未支持非嵌套的 WITH ORDINALITY 。</p>
{% highlight sql %}
SELECT users, tag
FROM Orders CROSS JOIN UNNEST(tags) AS t (tag)
{% endhighlight %}
</td>
</tr>
<tr>
- <td>
- <strong>Join with Table Function (UDTF)</strong><br>
- <span class="label label-primary">Batch</span> <span class="label label-primary">Streaming</span>
+ <td>
+ <strong>Join 表函数 (UDTF)</strong><br>
+ <span class="label label-primary">批处理</span> <span class="label label-primary">流处理</span>
</td>
- <td>
- <p>Joins a table with the results of a table function. Each row of the left (outer) table is joined with all rows produced by the corresponding call of the table function.</p>
- <p>User-defined table functions (UDTFs) must be registered before. See the <a href="{{ site.baseurl }}/dev/table/functions/udfs.html">UDF documentation</a> for details on how to specify and register UDTFs. </p>
+ <td>
+ <p>将表与表函数的结果进行 join 操作。左表（outer）中的每一行将会与调用表函数所产生的所有结果中相关联行进行 join 。</p>
+ <p>用户自定义表函数（ User-defined table functions，UDTFs ） 在执行前必须先注册。请参考 <a href="{{ site.baseurl }}/zh/dev/table/functions/udfs.html">UDF 文档</a> 以获取更多关于指定和注册UDF的信息 </p>
<p><b>Inner Join</b></p>
- <p>A row of the left (outer) table is dropped, if its table function call returns an empty result.</p>
+ <p>若表函数返回了空结果，左表（outer）的行将会被删除。</p>
{% highlight sql %}
SELECT users, tag
FROM Orders, LATERAL TABLE(unnest_udtf(tags)) t AS tag
{% endhighlight %}
<p><b>Left Outer Join</b></p>
- <p>If a table function call returns an empty result, the corresponding outer row is preserved and the result padded with null values.</p>
+ <p>若表函数返回了空结果，将会保留相对应的外部行并用空值填充结果。</p>
{% highlight sql %}
SELECT users, tag
FROM Orders LEFT JOIN LATERAL TABLE(unnest_udtf(tags)) t AS tag ON TRUE
{% endhighlight %}
- <p><b>Note:</b> Currently, only literal <code>TRUE</code> is supported as predicate for a left outer join against a lateral table.</p>
+ <p><b>注意：</b> 当前仅支持文本常量 <code>TRUE</code> 作为针对横向表的左外部联接的谓词。</p>
</td>
</tr>
<tr>
<td>
- <strong>Join with Temporal Table Function</strong><br>
- <span class="label label-primary">Streaming</span>
+ <strong>Join Temporal Tables 函数</strong><br>
+ <span class="label label-primary">流处理</span>
</td>
<td>
- <p><a href="{{ site.baseurl }}/dev/table/streaming/temporal_tables.html">Temporal tables</a> are tables that track changes over time.</p>
- <p>A <a href="{{ site.baseurl }}/dev/table/streaming/temporal_tables.html#temporal-table-functions">Temporal table function</a> provides access to the state of a temporal table at a specific point in time.
- The syntax to join a table with a temporal table function is the same as in <i>Join with Table Function</i>.</p>
+ <p><a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html">Temporal Tables</a> 是跟随时间变化而变化的表。</p>
+ <p><a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html#temporal-table-functions"> Temporal Tables 函数（ Temporal table function ）</a> 提供访问 Temporal Tables 在某一时间点的状态的能力。
+ 与 Temporal Tables 函数 join 的语法与 <i>Join 表函数</i> 一致。</p>
- <p><b>Note:</b> Currently only inner joins with temporal tables are supported.</p>
+ <p><b>注意：</b> 目前仅支持在 Temporal Tables 上的 inner join 。</p>
- <p>Assuming <i>Rates</i> is a <a href="{{ site.baseurl }}/dev/table/streaming/temporal_tables.html#temporal-table-functions">temporal table function</a>, the join can be expressed in SQL as follows:</p>
+ <p>加入 <i>Rates</i> 是一个 <a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html#temporal-table-functions"> Temporal Tables 函数</a>, join 可以使用SQL 进行如下的表达:</p>
Review comment:
```suggestion
<p>假如 <i>Rates</i> 是一个 <a href="{{ site.baseurl }}/zh/dev/table/streaming/temporal_tables.html#temporal-table-functions"> Temporal Tables 函数</a>, join 可以使用SQL 进行如下的表达:</p>
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570073257
<!--
Meta data
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/142809001 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:827c1dc7e424d9e89d5573fe5a466682271803f8 Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4092 TriggerType:PUSH TriggerID:827c1dc7e424d9e89d5573fe5a466682271803f8
Hash:827c1dc7e424d9e89d5573fe5a466682271803f8 Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/143077633 TriggerType:PUSH TriggerID:827c1dc7e424d9e89d5573fe5a466682271803f8
Hash:f481f0acdc30b1445a4de94de7ba4f2293305cbb Status:PENDING URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4094 TriggerType:PUSH TriggerID:f481f0acdc30b1445a4de94de7ba4f2293305cbb
Hash:f481f0acdc30b1445a4de94de7ba4f2293305cbb Status:PENDING URL:https://travis-ci.com/flink-ci/flink/builds/143085088 TriggerType:PUSH TriggerID:f481f0acdc30b1445a4de94de7ba4f2293305cbb
-->
## CI report:
* 8b4f68255a0a91f32757394d86405e46f60118c5 Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/142809001) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023)
* 827c1dc7e424d9e89d5573fe5a466682271803f8 Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/143077633) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4092)
* f481f0acdc30b1445a4de94de7ba4f2293305cbb Travis: [PENDING](https://travis-ci.com/flink-ci/flink/builds/143085088) Azure: [PENDING](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4094)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362367667
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -1116,68 +1111,68 @@ The start and end timestamps of group windows as well as time attributes can be
<code>HOP_START(time_attr, interval, interval)</code><br/>
<code>SESSION_START(time_attr, interval)</code><br/>
</td>
- <td><p>Returns the timestamp of the inclusive lower bound of the corresponding tumbling, hopping, or session window.</p></td>
+ <td><p>返回相对应的滚动，滑动和会话窗口范围内的下界时间戳。</p></td>
</tr>
<tr>
<td>
<code>TUMBLE_END(time_attr, interval)</code><br/>
<code>HOP_END(time_attr, interval, interval)</code><br/>
<code>SESSION_END(time_attr, interval)</code><br/>
</td>
- <td><p>Returns the timestamp of the <i>exclusive</i> upper bound of the corresponding tumbling, hopping, or session window.</p>
- <p><b>Note:</b> The exclusive upper bound timestamp <i>cannot</i> be used as a <a href="{{ site.baseurl }}/dev/table/streaming/time_attributes.html">rowtime attribute</a> in subsequent time-based operations, such as <a href="#joins">time-windowed joins</a> and <a href="#aggregations">group window or over window aggregations</a>.</p></td>
+ <td><p>返回相对应的滚动，滑动和会话窗口<i>范围以外</i>的上界时间戳。</p>
Review comment:
```suggestion
<td><p>返回相对应的滚动、滑动和会话窗口<i>范围以外</i>的上界时间戳。</p>
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362364561
##########
File path: docs/dev/table/sql/create.zh.md
##########
@@ -141,44 +141,44 @@ CREATE TABLE [catalog_name.][db_name.]table_name
{% endhighlight %}
-Creates a table with the given name. If a table with the same name already exists in the catalog, an exception is thrown.
+根据给定的表属性创建表。若数据库中已存在同名表会抛出异常。
**COMPUTED COLUMN**
-A computed column is a virtual column that is generated using the syntax "`column_name AS computed_column_expression`". It is generated from a non-query expression that uses other columns in the same table and is not physically stored within the table. For example, a computed column could be defined as `cost AS price * quantity`. The expression may contain any combination of physical column, constant, function, or variable. The expression cannot contain a subquery.
+计算列是一个使用 “`column_name AS computed_column_expression`” 语法生成的虚拟列。它由使用同一表中其他列的非查询表达式生成，并且不会在表中进行物理存储。例如，一个计算列可以使用 `cost AS price * quantity` 进行定义，这个表达式可以包含物理列、常量、函数或变量的任意组合，但这个表达式不能存在任何子查询。
-Computed columns are commonly used in Flink for defining [time attributes]({{ site.baseurl}}/dev/table/streaming/time_attributes.html) in CREATE TABLE statements.
-A [processing time attribute]({{ site.baseurl}}/dev/table/streaming/time_attributes.html#processing-time) can be defined easily via `proc AS PROCTIME()` using the system `PROCTIME()` function.
-On the other hand, computed column can be used to derive event time column because an event time column may need to be derived from existing fields, e.g. the original field is not `TIMESTAMP(3)` type or is nested in a JSON string.
+在 Flink 中计算列一般用于为 CREATE TABLE 语句定义 [时间属性]({{ site.baseurl}}/zh/dev/table/streaming/time_attributes.html)。
+[处理时间属性]({{ site.baseurl}}/zh/dev/table/streaming/time_attributes.html#processing-time) 可以简单地通过使用了系统函数 `PROCTIME()` 的 `proc AS PROCTIME()` 语句进行定义。
+另一方面，由于事件时间列可能需要从现有的字段中获得，因此计算列可用于获得事件时间列。例如，原始字段的类型不是 `TIMESTAMP(3)` 或嵌套在 JSON 字符串中。
-Notes:
+注意：
-- A computed column defined on a source table is computed after reading from the source, it can be used in the following SELECT query statements.
-- A computed column cannot be the target of an INSERT statement. In INSERT statements, the schema of SELECT clause should match the schema of the target table without computed columns.
+- 定义在一个数据源表（ source table ）上的计算列会在从数据源读取数据后被计算，它们可以在 SELECT 查询语句后使用。
+- 计算列不可以作为 INSERT 语句的目标，在 INSERT 语句中，SELECT 语句的结构（ schema ）需要与目标表不带有计算列的结构一致。
**WATERMARK**
-The `WATERMARK` defines the event time attributes of a table and takes the form `WATERMARK FOR rowtime_column_name AS watermark_strategy_expression`.
+`WATERMARK` 定义了表的事件时间属性，其形式为 `WATERMARK FOR rowtime_column_name AS watermark_strategy_expression` 。
-The `rowtime_column_name` defines an existing column that is marked as the event time attribute of the table. The column must be of type `TIMESTAMP(3)` and be a top-level column in the schema. It may be a computed column.
+`rowtime_column_name` 把一个现有的列定义为一个为表标记事件时间的属性。该列的类型必须为 `TIMESTAMP(3)`，且是结构中最高级别的列，它也可以是一个计算列。
-The `watermark_strategy_expression` defines the watermark generation strategy. It allows arbitrary non-query expression, including computed columns, to calculate the watermark. The expression return type must be TIMESTAMP(3), which represents the timestamp since the Epoch.
+`watermark_strategy_expression` 定义了 watermark 的生成策略。它允许使用包括计算列在内的任意非查询表达式来计算 watermark ；表达式的返回类型必须是表示了从起始点（ Epoch ）以来的时间戳的 TIMESTAMP(3) 。
-When using event time semantics, tables must contain an event time attribute and watermarking strategy.
+使用事件时间语义时，表必须包含事件时间属性和 watermark 策略。
-Flink provides several commonly used watermark strategies.
+Flink 提供了几种常用的 watermark 策略。
-- Strictly ascending timestamps: `WATERMARK FOR rowtime_column AS rowtime_column`.
+- 严格递增时间戳： `WATERMARK FOR rowtime_column AS rowtime_column`。
- Emits a watermark of the maximum observed timestamp so far. Rows that have a timestamp smaller to the max timestamp are not late.
+ 发出到目前为止已观察到的最大时间戳的 watermark ，时间戳小于最大时间戳的行不会迟到。
-- Ascending timestamps: `WATERMARK FOR rowtime_column AS rowtime_column - INTERVAL '0.001' SECOND`.
+- 递增时间戳： `WATERMARK FOR rowtime_column AS rowtime_column - INTERVAL '0.001' SECOND`。
- Emits a watermark of the maximum observed timestamp so far minus 1. Rows that have a timestamp equal to the max timestamp are not late.
+ 发出到目前为止已观察到的最大时间戳减 1 的 watermark ，时间戳等于最大时间戳的行不会迟到。
-- Bounded out of orderness timestamps: `WATERMARK FOR rowtime_column AS rowtimeField - INTERVAL 'string' timeUnit`.
+- 有界有序时间戳： `WATERMARK FOR rowtime_column AS rowtimeField - INTERVAL 'string' timeUnit`。
Review comment:
```suggestion
- 有界乱序时间戳： `WATERMARK FOR rowtime_column AS rowtimeField - INTERVAL 'string' timeUnit`。
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362363880
##########
File path: docs/dev/table/sql/create.zh.md
##########
@@ -141,44 +141,44 @@ CREATE TABLE [catalog_name.][db_name.]table_name
{% endhighlight %}
-Creates a table with the given name. If a table with the same name already exists in the catalog, an exception is thrown.
+根据给定的表属性创建表。若数据库中已存在同名表会抛出异常。
Review comment:
根据指定的表名创建一个表，如果同名表已经在 catalog 中存在了，则无法注册。
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot commented on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
flinkbot commented on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570073257
<!--
Meta data
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:UNKNOWN URL:TBD TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
-->
## CI report:
* 8b4f68255a0a91f32757394d86405e46f60118c5 UNKNOWN
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570980651
Hi @ousheobin thanks for the updating, the chagnes looks good to me in general. I will make some minor change and merge it.
Btw, please use `git rebase` instead of `git merge`, we should always avoid merge commits in the git history.
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362366207
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -106,7 +106,7 @@ tableEnv.connect(new FileSystem("/path/to/file"))
.withSchema(schema)
.createTemporaryTable("RubberOrders")
-// run a SQL update query on the Table and emit the result to the TableSink
+// 在表上执行 SQL 更新操纵，并把结果发出到 TableSink
Review comment:
```suggestion
// 在表上执行 SQL 更新操作，并把结果发出到 TableSink
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362364696
##########
File path: docs/dev/table/sql/drop.zh.md
##########
@@ -110,34 +110,34 @@ Flink SQL> SHOW TABLES;
</div>
</div>
-## DROP TABLE
+## 删除表
{% highlight sql %}
DROP TABLE [IF EXISTS] [catalog_name.][db_name.]table_name
{% endhighlight %}
-Drop a table with the given table name. If the table to drop does not exist, an exception is thrown.
+根据给定的表名删除某个表。若需要删除的表不存在，则抛出异常。
**IF EXISTS**
-If the table does not exist, nothing happens.
+表不存在时不会进行任何操作。
-## DROP DATABASE
+## 删除数据库
Review comment:
revert.
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570073257
<!--
Meta data
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/142809001 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:827c1dc7e424d9e89d5573fe5a466682271803f8 Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4092 TriggerType:PUSH TriggerID:827c1dc7e424d9e89d5573fe5a466682271803f8
Hash:827c1dc7e424d9e89d5573fe5a466682271803f8 Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/143077633 TriggerType:PUSH TriggerID:827c1dc7e424d9e89d5573fe5a466682271803f8
Hash:f481f0acdc30b1445a4de94de7ba4f2293305cbb Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4094 TriggerType:PUSH TriggerID:f481f0acdc30b1445a4de94de7ba4f2293305cbb
Hash:f481f0acdc30b1445a4de94de7ba4f2293305cbb Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/143085088 TriggerType:PUSH TriggerID:f481f0acdc30b1445a4de94de7ba4f2293305cbb
-->
## CI report:
* 8b4f68255a0a91f32757394d86405e46f60118c5 Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/142809001) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023)
* 827c1dc7e424d9e89d5573fe5a466682271803f8 Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/143077633) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4092)
* f481f0acdc30b1445a4de94de7ba4f2293305cbb Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/143085088) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4094)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362363493
##########
File path: docs/dev/table/sql/alter.zh.md
##########
@@ -110,28 +110,28 @@ NewOrders
</div>
</div>
-## ALTER TABLE
+## 修改表
Review comment:
```suggestion
## ALTER TABLE
```
Please revert. This refers to the `ALTER TABLE` statement which shouldn't be translated.
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570073257
<!--
Meta data
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/142809001 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:827c1dc7e424d9e89d5573fe5a466682271803f8 Status:PENDING URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4092 TriggerType:PUSH TriggerID:827c1dc7e424d9e89d5573fe5a466682271803f8
Hash:827c1dc7e424d9e89d5573fe5a466682271803f8 Status:PENDING URL:https://travis-ci.com/flink-ci/flink/builds/143077633 TriggerType:PUSH TriggerID:827c1dc7e424d9e89d5573fe5a466682271803f8
-->
## CI report:
* 8b4f68255a0a91f32757394d86405e46f60118c5 Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/142809001) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023)
* 827c1dc7e424d9e89d5573fe5a466682271803f8 Travis: [PENDING](https://travis-ci.com/flink-ci/flink/builds/143077633) Azure: [PENDING](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4092)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362364684
##########
File path: docs/dev/table/sql/drop.zh.md
##########
@@ -110,34 +110,34 @@ Flink SQL> SHOW TABLES;
</div>
</div>
-## DROP TABLE
+## 删除表
Review comment:
revert.
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362366196
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -134,7 +134,7 @@ t_env.connect(FileSystem().path("/path/to/file")))
.field("amount", DataTypes.BIGINT()))
.create_temporary_table("RubberOrders")
-# run a SQL update query on the Table and emit the result to the TableSink
+# 在表上执行 SQL 更新操纵，并把结果发出到 TableSink
Review comment:
```suggestion
# 在表上执行 SQL 更新操作，并把结果发出到 TableSink
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362364507
##########
File path: docs/dev/table/sql/create.zh.md
##########
@@ -141,44 +141,44 @@ CREATE TABLE [catalog_name.][db_name.]table_name
{% endhighlight %}
-Creates a table with the given name. If a table with the same name already exists in the catalog, an exception is thrown.
+根据给定的表属性创建表。若数据库中已存在同名表会抛出异常。
**COMPUTED COLUMN**
-A computed column is a virtual column that is generated using the syntax "`column_name AS computed_column_expression`". It is generated from a non-query expression that uses other columns in the same table and is not physically stored within the table. For example, a computed column could be defined as `cost AS price * quantity`. The expression may contain any combination of physical column, constant, function, or variable. The expression cannot contain a subquery.
+计算列是一个使用 “`column_name AS computed_column_expression`” 语法生成的虚拟列。它由使用同一表中其他列的非查询表达式生成，并且不会在表中进行物理存储。例如，一个计算列可以使用 `cost AS price * quantity` 进行定义，这个表达式可以包含物理列、常量、函数或变量的任意组合，但这个表达式不能存在任何子查询。
-Computed columns are commonly used in Flink for defining [time attributes]({{ site.baseurl}}/dev/table/streaming/time_attributes.html) in CREATE TABLE statements.
-A [processing time attribute]({{ site.baseurl}}/dev/table/streaming/time_attributes.html#processing-time) can be defined easily via `proc AS PROCTIME()` using the system `PROCTIME()` function.
-On the other hand, computed column can be used to derive event time column because an event time column may need to be derived from existing fields, e.g. the original field is not `TIMESTAMP(3)` type or is nested in a JSON string.
+在 Flink 中计算列一般用于为 CREATE TABLE 语句定义 [时间属性]({{ site.baseurl}}/zh/dev/table/streaming/time_attributes.html)。
+[处理时间属性]({{ site.baseurl}}/zh/dev/table/streaming/time_attributes.html#processing-time) 可以简单地通过使用了系统函数 `PROCTIME()` 的 `proc AS PROCTIME()` 语句进行定义。
+另一方面，由于事件时间列可能需要从现有的字段中获得，因此计算列可用于获得事件时间列。例如，原始字段的类型不是 `TIMESTAMP(3)` 或嵌套在 JSON 字符串中。
-Notes:
+注意：
-- A computed column defined on a source table is computed after reading from the source, it can be used in the following SELECT query statements.
-- A computed column cannot be the target of an INSERT statement. In INSERT statements, the schema of SELECT clause should match the schema of the target table without computed columns.
+- 定义在一个数据源表（ source table ）上的计算列会在从数据源读取数据后被计算，它们可以在 SELECT 查询语句后使用。
+- 计算列不可以作为 INSERT 语句的目标，在 INSERT 语句中，SELECT 语句的结构（ schema ）需要与目标表不带有计算列的结构一致。
**WATERMARK**
-The `WATERMARK` defines the event time attributes of a table and takes the form `WATERMARK FOR rowtime_column_name AS watermark_strategy_expression`.
+`WATERMARK` 定义了表的事件时间属性，其形式为 `WATERMARK FOR rowtime_column_name AS watermark_strategy_expression` 。
-The `rowtime_column_name` defines an existing column that is marked as the event time attribute of the table. The column must be of type `TIMESTAMP(3)` and be a top-level column in the schema. It may be a computed column.
+`rowtime_column_name` 把一个现有的列定义为一个为表标记事件时间的属性。该列的类型必须为 `TIMESTAMP(3)`，且是结构中最高级别的列，它也可以是一个计算列。
-The `watermark_strategy_expression` defines the watermark generation strategy. It allows arbitrary non-query expression, including computed columns, to calculate the watermark. The expression return type must be TIMESTAMP(3), which represents the timestamp since the Epoch.
+`watermark_strategy_expression` 定义了 watermark 的生成策略。它允许使用包括计算列在内的任意非查询表达式来计算 watermark ；表达式的返回类型必须是表示了从起始点（ Epoch ）以来的时间戳的 TIMESTAMP(3) 。
-When using event time semantics, tables must contain an event time attribute and watermarking strategy.
+使用事件时间语义时，表必须包含事件时间属性和 watermark 策略。
-Flink provides several commonly used watermark strategies.
+Flink 提供了几种常用的 watermark 策略。
-- Strictly ascending timestamps: `WATERMARK FOR rowtime_column AS rowtime_column`.
+- 严格递增时间戳： `WATERMARK FOR rowtime_column AS rowtime_column`。
- Emits a watermark of the maximum observed timestamp so far. Rows that have a timestamp smaller to the max timestamp are not late.
+ 发出到目前为止已观察到的最大时间戳的 watermark ，时间戳小于最大时间戳的行不会迟到。
Review comment:
```suggestion
发出到目前为止已观察到的最大时间戳的 watermark ，时间戳小于最大时间戳的行被认为没有迟到。
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362364132
##########
File path: docs/dev/table/sql/create.zh.md
##########
@@ -141,44 +141,44 @@ CREATE TABLE [catalog_name.][db_name.]table_name
{% endhighlight %}
-Creates a table with the given name. If a table with the same name already exists in the catalog, an exception is thrown.
+根据给定的表属性创建表。若数据库中已存在同名表会抛出异常。
**COMPUTED COLUMN**
-A computed column is a virtual column that is generated using the syntax "`column_name AS computed_column_expression`". It is generated from a non-query expression that uses other columns in the same table and is not physically stored within the table. For example, a computed column could be defined as `cost AS price * quantity`. The expression may contain any combination of physical column, constant, function, or variable. The expression cannot contain a subquery.
+计算列是一个使用 “`column_name AS computed_column_expression`” 语法生成的虚拟列。它由使用同一表中其他列的非查询表达式生成，并且不会在表中进行物理存储。例如，一个计算列可以使用 `cost AS price * quantity` 进行定义，这个表达式可以包含物理列、常量、函数或变量的任意组合，但这个表达式不能存在任何子查询。
-Computed columns are commonly used in Flink for defining [time attributes]({{ site.baseurl}}/dev/table/streaming/time_attributes.html) in CREATE TABLE statements.
-A [processing time attribute]({{ site.baseurl}}/dev/table/streaming/time_attributes.html#processing-time) can be defined easily via `proc AS PROCTIME()` using the system `PROCTIME()` function.
-On the other hand, computed column can be used to derive event time column because an event time column may need to be derived from existing fields, e.g. the original field is not `TIMESTAMP(3)` type or is nested in a JSON string.
+在 Flink 中计算列一般用于为 CREATE TABLE 语句定义 [时间属性]({{ site.baseurl}}/zh/dev/table/streaming/time_attributes.html)。
+[处理时间属性]({{ site.baseurl}}/zh/dev/table/streaming/time_attributes.html#processing-time) 可以简单地通过使用了系统函数 `PROCTIME()` 的 `proc AS PROCTIME()` 语句进行定义。
+另一方面，由于事件时间列可能需要从现有的字段中获得，因此计算列可用于获得事件时间列。例如，原始字段的类型不是 `TIMESTAMP(3)` 或嵌套在 JSON 字符串中。
-Notes:
+注意：
-- A computed column defined on a source table is computed after reading from the source, it can be used in the following SELECT query statements.
-- A computed column cannot be the target of an INSERT statement. In INSERT statements, the schema of SELECT clause should match the schema of the target table without computed columns.
+- 定义在一个数据源表（ source table ）上的计算列会在从数据源读取数据后被计算，它们可以在 SELECT 查询语句后使用。
+- 计算列不可以作为 INSERT 语句的目标，在 INSERT 语句中，SELECT 语句的结构（ schema ）需要与目标表不带有计算列的结构一致。
**WATERMARK**
-The `WATERMARK` defines the event time attributes of a table and takes the form `WATERMARK FOR rowtime_column_name AS watermark_strategy_expression`.
+`WATERMARK` 定义了表的事件时间属性，其形式为 `WATERMARK FOR rowtime_column_name AS watermark_strategy_expression` 。
-The `rowtime_column_name` defines an existing column that is marked as the event time attribute of the table. The column must be of type `TIMESTAMP(3)` and be a top-level column in the schema. It may be a computed column.
+`rowtime_column_name` 把一个现有的列定义为一个为表标记事件时间的属性。该列的类型必须为 `TIMESTAMP(3)`，且是结构中最高级别的列，它也可以是一个计算列。
Review comment:
```suggestion
`rowtime_column_name` 把一个现有的列定义为一个为表标记事件时间的属性。该列的类型必须为 `TIMESTAMP(3)`，且是 schema 中的顶层列，它也可以是一个计算列。
```
schema 也可以不翻译。
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362364283
##########
File path: docs/dev/table/sql/create.zh.md
##########
@@ -141,44 +141,44 @@ CREATE TABLE [catalog_name.][db_name.]table_name
{% endhighlight %}
-Creates a table with the given name. If a table with the same name already exists in the catalog, an exception is thrown.
+根据给定的表属性创建表。若数据库中已存在同名表会抛出异常。
**COMPUTED COLUMN**
-A computed column is a virtual column that is generated using the syntax "`column_name AS computed_column_expression`". It is generated from a non-query expression that uses other columns in the same table and is not physically stored within the table. For example, a computed column could be defined as `cost AS price * quantity`. The expression may contain any combination of physical column, constant, function, or variable. The expression cannot contain a subquery.
+计算列是一个使用 “`column_name AS computed_column_expression`” 语法生成的虚拟列。它由使用同一表中其他列的非查询表达式生成，并且不会在表中进行物理存储。例如，一个计算列可以使用 `cost AS price * quantity` 进行定义，这个表达式可以包含物理列、常量、函数或变量的任意组合，但这个表达式不能存在任何子查询。
-Computed columns are commonly used in Flink for defining [time attributes]({{ site.baseurl}}/dev/table/streaming/time_attributes.html) in CREATE TABLE statements.
-A [processing time attribute]({{ site.baseurl}}/dev/table/streaming/time_attributes.html#processing-time) can be defined easily via `proc AS PROCTIME()` using the system `PROCTIME()` function.
-On the other hand, computed column can be used to derive event time column because an event time column may need to be derived from existing fields, e.g. the original field is not `TIMESTAMP(3)` type or is nested in a JSON string.
+在 Flink 中计算列一般用于为 CREATE TABLE 语句定义 [时间属性]({{ site.baseurl}}/zh/dev/table/streaming/time_attributes.html)。
+[处理时间属性]({{ site.baseurl}}/zh/dev/table/streaming/time_attributes.html#processing-time) 可以简单地通过使用了系统函数 `PROCTIME()` 的 `proc AS PROCTIME()` 语句进行定义。
+另一方面，由于事件时间列可能需要从现有的字段中获得，因此计算列可用于获得事件时间列。例如，原始字段的类型不是 `TIMESTAMP(3)` 或嵌套在 JSON 字符串中。
-Notes:
+注意：
-- A computed column defined on a source table is computed after reading from the source, it can be used in the following SELECT query statements.
-- A computed column cannot be the target of an INSERT statement. In INSERT statements, the schema of SELECT clause should match the schema of the target table without computed columns.
+- 定义在一个数据源表（ source table ）上的计算列会在从数据源读取数据后被计算，它们可以在 SELECT 查询语句后使用。
+- 计算列不可以作为 INSERT 语句的目标，在 INSERT 语句中，SELECT 语句的结构（ schema ）需要与目标表不带有计算列的结构一致。
**WATERMARK**
-The `WATERMARK` defines the event time attributes of a table and takes the form `WATERMARK FOR rowtime_column_name AS watermark_strategy_expression`.
+`WATERMARK` 定义了表的事件时间属性，其形式为 `WATERMARK FOR rowtime_column_name AS watermark_strategy_expression` 。
-The `rowtime_column_name` defines an existing column that is marked as the event time attribute of the table. The column must be of type `TIMESTAMP(3)` and be a top-level column in the schema. It may be a computed column.
+`rowtime_column_name` 把一个现有的列定义为一个为表标记事件时间的属性。该列的类型必须为 `TIMESTAMP(3)`，且是结构中最高级别的列，它也可以是一个计算列。
-The `watermark_strategy_expression` defines the watermark generation strategy. It allows arbitrary non-query expression, including computed columns, to calculate the watermark. The expression return type must be TIMESTAMP(3), which represents the timestamp since the Epoch.
+`watermark_strategy_expression` 定义了 watermark 的生成策略。它允许使用包括计算列在内的任意非查询表达式来计算 watermark ；表达式的返回类型必须是表示了从起始点（ Epoch ）以来的时间戳的 TIMESTAMP(3) 。
Review comment:
```suggestion
`watermark_strategy_expression` 定义了 watermark 的生成策略。它允许使用包括计算列在内的任意非查询表达式来计算 watermark ；表达式的返回类型必须是 `TIMESTAMP(3)`，表示了从 Epoch 以来的经过的时间。
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362367550
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -1063,49 +1058,49 @@ val result1 = tableEnv.sqlQuery(
{% top %}
-### Group Windows
+### 分组窗口
-Group windows are defined in the `GROUP BY` clause of a SQL query. Just like queries with regular `GROUP BY` clauses, queries with a `GROUP BY` clause that includes a group window function compute a single result row per group. The following group windows functions are supported for SQL on batch and streaming tables.
+SQL 查询的分组窗口是通过 `GROUP BY` 子句定义的。类似于使用常规 `GROUP BY` 语句的查询，窗口分组语句的 `GROUP BY` 子句中带有一个窗口函数为每个分组计算出一个结果。以下是批处理表和流处理表支持的分组窗口函数：
<table class="table table-bordered">
<thead>
<tr>
- <th class="text-left" style="width: 30%">Group Window Function</th>
- <th class="text-left">Description</th>
+ <th class="text-left" style="width: 30%">分组窗口函数</th>
+ <th class="text-left">描述</th>
</tr>
</thead>
<tbody>
<tr>
<td><code>TUMBLE(time_attr, interval)</code></td>
- <td>Defines a tumbling time window. A tumbling time window assigns rows to non-overlapping, continuous windows with a fixed duration (<code>interval</code>). For example, a tumbling window of 5 minutes groups rows in 5 minutes intervals. Tumbling windows can be defined on event-time (stream + batch) or processing-time (stream).</td>
+ <td>定义一个滚动窗口。滚动窗口把行分配到有固定持续时间（ <code>interval</code> ）的不重叠的连续窗口。比如，5 分钟的滚动窗口以 5 分钟为间隔对行进行分组。滚动窗口可以定义在事件时间（批处理、流处理）或处理时间（流处理）上。</td>
</tr>
<tr>
<td><code>HOP(time_attr, interval, interval)</code></td>
- <td>Defines a hopping time window (called sliding window in the Table API). A hopping time window has a fixed duration (second <code>interval</code> parameter) and hops by a specified hop interval (first <code>interval</code> parameter). If the hop interval is smaller than the window size, hopping windows are overlapping. Thus, rows can be assigned to multiple windows. For example, a hopping window of 15 minutes size and 5 minute hop interval assigns each row to 3 different windows of 15 minute size, which are evaluated in an interval of 5 minutes. Hopping windows can be defined on event-time (stream + batch) or processing-time (stream).</td>
+ <td>定义一个跳跃的时间窗口（在 Table API 中称为滑动窗口）。滑动窗口有一个固定的持续时间（ 第二个 <code>interval</code> 参数 ）以及一个滑动的间隔（第一个 code>interval</code> 参数 ）。若滑动间隔小于窗口的持续时间，滑动窗口则会出现重叠；因此，行将会被分配到多个窗口中。比如，一个大小为 15 分组的滑动窗口，其滑动间隔为 5 分钟，将会把每一行数据分配到 3 个 15 分钟的窗口中。滑动窗口可以定义在事件时间（批处理、流处理）或处理时间（流处理）上。</td>
Review comment:
```suggestion
<td>定义一个跳跃的时间窗口（在 Table API 中称为滑动窗口）。滑动窗口有一个固定的持续时间（ 第二个 <code>interval</code> 参数 ）以及一个滑动的间隔（第一个 <code>interval</code> 参数 ）。若滑动间隔小于窗口的持续时间，滑动窗口则会出现重叠；因此，行将会被分配到多个窗口中。比如，一个大小为 15 分组的滑动窗口，其滑动间隔为 5 分钟，将会把每一行数据分配到 3 个 15 分钟的窗口中。滑动窗口可以定义在事件时间（批处理、流处理）或处理时间（流处理）上。</td>
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] ousheobin commented on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
ousheobin commented on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570491588
Hi @wuchong . Thanks for your review. Because I have some personal matters yesterday and I will help to update the content base on your comments and translate the corresponding content in #10732 by this week. Please let me know if you have any concern on it.
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362363780
##########
File path: docs/dev/table/sql/create.zh.md
##########
@@ -118,7 +118,7 @@ Flink SQL> INSERT INTO RubberOrders SELECT product, amount FROM Orders WHERE pro
{% top %}
-## CREATE TABLE
+## 创建表
Review comment:
revert.
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570499256
Thanks @ousheobin . Please also translate the corresponding content in https://github.com/apache/flink/commit/660901699f9174d80ee40616f3efd493e1cee324#diff-32af0e13b8a200b0e205ed866c49670f.
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] ousheobin commented on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
ousheobin commented on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570500775
@wuchong Sure, will do it asap.
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362364476
##########
File path: docs/dev/table/sql/create.zh.md
##########
@@ -141,44 +141,44 @@ CREATE TABLE [catalog_name.][db_name.]table_name
{% endhighlight %}
-Creates a table with the given name. If a table with the same name already exists in the catalog, an exception is thrown.
+根据给定的表属性创建表。若数据库中已存在同名表会抛出异常。
**COMPUTED COLUMN**
-A computed column is a virtual column that is generated using the syntax "`column_name AS computed_column_expression`". It is generated from a non-query expression that uses other columns in the same table and is not physically stored within the table. For example, a computed column could be defined as `cost AS price * quantity`. The expression may contain any combination of physical column, constant, function, or variable. The expression cannot contain a subquery.
+计算列是一个使用 “`column_name AS computed_column_expression`” 语法生成的虚拟列。它由使用同一表中其他列的非查询表达式生成，并且不会在表中进行物理存储。例如，一个计算列可以使用 `cost AS price * quantity` 进行定义，这个表达式可以包含物理列、常量、函数或变量的任意组合，但这个表达式不能存在任何子查询。
-Computed columns are commonly used in Flink for defining [time attributes]({{ site.baseurl}}/dev/table/streaming/time_attributes.html) in CREATE TABLE statements.
-A [processing time attribute]({{ site.baseurl}}/dev/table/streaming/time_attributes.html#processing-time) can be defined easily via `proc AS PROCTIME()` using the system `PROCTIME()` function.
-On the other hand, computed column can be used to derive event time column because an event time column may need to be derived from existing fields, e.g. the original field is not `TIMESTAMP(3)` type or is nested in a JSON string.
+在 Flink 中计算列一般用于为 CREATE TABLE 语句定义 [时间属性]({{ site.baseurl}}/zh/dev/table/streaming/time_attributes.html)。
+[处理时间属性]({{ site.baseurl}}/zh/dev/table/streaming/time_attributes.html#processing-time) 可以简单地通过使用了系统函数 `PROCTIME()` 的 `proc AS PROCTIME()` 语句进行定义。
+另一方面，由于事件时间列可能需要从现有的字段中获得，因此计算列可用于获得事件时间列。例如，原始字段的类型不是 `TIMESTAMP(3)` 或嵌套在 JSON 字符串中。
-Notes:
+注意：
-- A computed column defined on a source table is computed after reading from the source, it can be used in the following SELECT query statements.
-- A computed column cannot be the target of an INSERT statement. In INSERT statements, the schema of SELECT clause should match the schema of the target table without computed columns.
+- 定义在一个数据源表（ source table ）上的计算列会在从数据源读取数据后被计算，它们可以在 SELECT 查询语句后使用。
+- 计算列不可以作为 INSERT 语句的目标，在 INSERT 语句中，SELECT 语句的结构（ schema ）需要与目标表不带有计算列的结构一致。
**WATERMARK**
-The `WATERMARK` defines the event time attributes of a table and takes the form `WATERMARK FOR rowtime_column_name AS watermark_strategy_expression`.
+`WATERMARK` 定义了表的事件时间属性，其形式为 `WATERMARK FOR rowtime_column_name AS watermark_strategy_expression` 。
-The `rowtime_column_name` defines an existing column that is marked as the event time attribute of the table. The column must be of type `TIMESTAMP(3)` and be a top-level column in the schema. It may be a computed column.
+`rowtime_column_name` 把一个现有的列定义为一个为表标记事件时间的属性。该列的类型必须为 `TIMESTAMP(3)`，且是结构中最高级别的列，它也可以是一个计算列。
-The `watermark_strategy_expression` defines the watermark generation strategy. It allows arbitrary non-query expression, including computed columns, to calculate the watermark. The expression return type must be TIMESTAMP(3), which represents the timestamp since the Epoch.
+`watermark_strategy_expression` 定义了 watermark 的生成策略。它允许使用包括计算列在内的任意非查询表达式来计算 watermark ；表达式的返回类型必须是表示了从起始点（ Epoch ）以来的时间戳的 TIMESTAMP(3) 。
-When using event time semantics, tables must contain an event time attribute and watermarking strategy.
+使用事件时间语义时，表必须包含事件时间属性和 watermark 策略。
-Flink provides several commonly used watermark strategies.
+Flink 提供了几种常用的 watermark 策略。
-- Strictly ascending timestamps: `WATERMARK FOR rowtime_column AS rowtime_column`.
+- 严格递增时间戳： `WATERMARK FOR rowtime_column AS rowtime_column`。
- Emits a watermark of the maximum observed timestamp so far. Rows that have a timestamp smaller to the max timestamp are not late.
+ 发出到目前为止已观察到的最大时间戳的 watermark ，时间戳小于最大时间戳的行不会迟到。
-- Ascending timestamps: `WATERMARK FOR rowtime_column AS rowtime_column - INTERVAL '0.001' SECOND`.
+- 递增时间戳： `WATERMARK FOR rowtime_column AS rowtime_column - INTERVAL '0.001' SECOND`。
- Emits a watermark of the maximum observed timestamp so far minus 1. Rows that have a timestamp equal to the max timestamp are not late.
+ 发出到目前为止已观察到的最大时间戳减 1 的 watermark ，时间戳等于最大时间戳的行不会迟到。
Review comment:
```suggestion
发出到目前为止已观察到的最大时间戳减 1 的 watermark ，时间戳等于或小于最大时间戳的行被认为没有迟到。
```
原文少了 `equal and smaller to the max..`， 请帮忙修改下英文原文。
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570073257
<!--
Meta data
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:PENDING URL:https://travis-ci.com/flink-ci/flink/builds/142809001 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:PENDING URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
-->
## CI report:
* 8b4f68255a0a91f32757394d86405e46f60118c5 Travis: [PENDING](https://travis-ci.com/flink-ci/flink/builds/142809001) Azure: [PENDING](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570073257
<!--
Meta data
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/142809001 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:827c1dc7e424d9e89d5573fe5a466682271803f8 Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4092 TriggerType:PUSH TriggerID:827c1dc7e424d9e89d5573fe5a466682271803f8
Hash:827c1dc7e424d9e89d5573fe5a466682271803f8 Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/143077633 TriggerType:PUSH TriggerID:827c1dc7e424d9e89d5573fe5a466682271803f8
-->
## CI report:
* 8b4f68255a0a91f32757394d86405e46f60118c5 Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/142809001) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023)
* 827c1dc7e424d9e89d5573fe5a466682271803f8 Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/143077633) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4092)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570073257
<!--
Meta data
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/142809001 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:827c1dc7e424d9e89d5573fe5a466682271803f8 Status:UNKNOWN URL:TBD TriggerType:PUSH TriggerID:827c1dc7e424d9e89d5573fe5a466682271803f8
-->
## CI report:
* 8b4f68255a0a91f32757394d86405e46f60118c5 Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/142809001) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023)
* 827c1dc7e424d9e89d5573fe5a466682271803f8 UNKNOWN
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362367142
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -863,33 +861,33 @@ FROM (
WHERE rownum <= N [AND conditions]
{% endhighlight %}
-**Parameter Specification:**
+**参数说明：**
-- `ROW_NUMBER()`: Assigns an unique, sequential number to each row, starting with one, according to the ordering of rows within the partition. Currently, we only support `ROW_NUMBER` as the over window function. In the future, we will support `RANK()` and `DENSE_RANK()`.
-- `PARTITION BY col1[, col2...]`: Specifies the partition columns. Each partition will have a Top-N result.
-- `ORDER BY col1 [asc|desc][, col2 [asc|desc]...]`: Specifies the ordering columns. The ordering directions can be different on different columns.
-- `WHERE rownum <= N`: The `rownum <= N` is required for Flink to recognize this query is a Top-N query. The N represents the N smallest or largest records will be retained.
-- `[AND conditions]`: It is free to add other conditions in the where clause, but the other conditions can only be combined with `rownum <= N` using `AND` conjunction.
+- `ROW_NUMBER()`: 根据当前分区内的各行的顺序从第一行开始，依次为每一行分配一个唯一且连续的号码。目前，我们只支持 `ROW_NUMBER` 在 over 窗口函数中使用。未来将会支持 `RANK()` 和 `DENSE_RANK()`函数。
+- `PARTITION BY col1[, col2...]`: 指定分区列，每个分区都将会有一个 Top-N 结果。
+- `ORDER BY col1 [asc|desc][, col2 [asc|desc]...]`: 指定排序列，不同列的排序方式可以不一样。
Review comment:
```suggestion
- `ORDER BY col1 [asc|desc][, col2 [asc|desc]...]`: 指定排序列，不同列的排序方向可以不一样。
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362367656
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -1116,68 +1111,68 @@ The start and end timestamps of group windows as well as time attributes can be
<code>HOP_START(time_attr, interval, interval)</code><br/>
<code>SESSION_START(time_attr, interval)</code><br/>
</td>
- <td><p>Returns the timestamp of the inclusive lower bound of the corresponding tumbling, hopping, or session window.</p></td>
+ <td><p>返回相对应的滚动，滑动和会话窗口范围内的下界时间戳。</p></td>
Review comment:
```suggestion
<td><p>返回相对应的滚动、滑动和会话窗口范围内的下界时间戳。</p></td>
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362367444
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -1236,25 +1231,25 @@ val result4 = tableEnv.sqlQuery(
{% top %}
-### Pattern Recognition
+## 模式匹配
Review comment:
```suggestion
### 模式匹配
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong closed pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong closed pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362367821
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -1116,68 +1111,68 @@ The start and end timestamps of group windows as well as time attributes can be
<code>HOP_START(time_attr, interval, interval)</code><br/>
<code>SESSION_START(time_attr, interval)</code><br/>
</td>
- <td><p>Returns the timestamp of the inclusive lower bound of the corresponding tumbling, hopping, or session window.</p></td>
+ <td><p>返回相对应的滚动，滑动和会话窗口范围内的下界时间戳。</p></td>
</tr>
<tr>
<td>
<code>TUMBLE_END(time_attr, interval)</code><br/>
<code>HOP_END(time_attr, interval, interval)</code><br/>
<code>SESSION_END(time_attr, interval)</code><br/>
</td>
- <td><p>Returns the timestamp of the <i>exclusive</i> upper bound of the corresponding tumbling, hopping, or session window.</p>
- <p><b>Note:</b> The exclusive upper bound timestamp <i>cannot</i> be used as a <a href="{{ site.baseurl }}/dev/table/streaming/time_attributes.html">rowtime attribute</a> in subsequent time-based operations, such as <a href="#joins">time-windowed joins</a> and <a href="#aggregations">group window or over window aggregations</a>.</p></td>
+ <td><p>返回相对应的滚动，滑动和会话窗口<i>范围以外</i>的上界时间戳。</p>
+ <p><b>注意：</b> 范围以外的上界时间戳<i>不可以</i> 在随后基于时间的操作中，作为 <a href="{{ site.baseurl }}/zh/dev/table/streaming/time_attributes.html">行时间属性</a> 使用，比如 <a href="#joins">基于时间窗口的 join </a> 以及 <a href="#aggregations">分组窗口或分组窗口上的聚合</a>。</p></td>
</tr>
<tr>
<td>
<code>TUMBLE_ROWTIME(time_attr, interval)</code><br/>
<code>HOP_ROWTIME(time_attr, interval, interval)</code><br/>
<code>SESSION_ROWTIME(time_attr, interval)</code><br/>
</td>
- <td><p>Returns the timestamp of the <i>inclusive</i> upper bound of the corresponding tumbling, hopping, or session window.</p>
- <p>The resulting attribute is a <a href="{{ site.baseurl }}/dev/table/streaming/time_attributes.html">rowtime attribute</a> that can be used in subsequent time-based operations such as <a href="#joins">time-windowed joins</a> and <a href="#aggregations">group window or over window aggregations</a>.</p></td>
+ <td><p>返回相对应的滚动，滑动和会话窗口<i>范围以内</i>的上界时间戳。</p>
+ <p>结果属性是一个可用于后续需要基于时间的操作的<a href="{{ site.baseurl }}/zh/dev/table/streaming/time_attributes.html">行时间属性</a>，比如<a href="#joins">基于时间窗口的 join </a> 以及 <a href="#aggregations">分组窗口或分组窗口上的聚合</a>。</p></td>
Review comment:
```suggestion
<p>返回的是一个可用于后续需要基于时间的操作的<a href="{{ site.baseurl }}/zh/dev/table/streaming/time_attributes.html">时间属性（rowtime attribute）</a>，比如<a href="#joins">基于时间窗口的 join </a> 以及 <a href="#aggregations">分组窗口或分组窗口上的聚合</a>。</p></td>
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570073257
<!--
Meta data
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/142809001 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:827c1dc7e424d9e89d5573fe5a466682271803f8 Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4092 TriggerType:PUSH TriggerID:827c1dc7e424d9e89d5573fe5a466682271803f8
Hash:827c1dc7e424d9e89d5573fe5a466682271803f8 Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/143077633 TriggerType:PUSH TriggerID:827c1dc7e424d9e89d5573fe5a466682271803f8
Hash:f481f0acdc30b1445a4de94de7ba4f2293305cbb Status:UNKNOWN URL:TBD TriggerType:PUSH TriggerID:f481f0acdc30b1445a4de94de7ba4f2293305cbb
-->
## CI report:
* 8b4f68255a0a91f32757394d86405e46f60118c5 Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/142809001) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023)
* 827c1dc7e424d9e89d5573fe5a466682271803f8 Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/143077633) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4092)
* f481f0acdc30b1445a4de94de7ba4f2293305cbb UNKNOWN
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570488961
Hi @ousheobin , do you have time to update this PR?
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570073257
<!--
Meta data
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/142809001 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
-->
## CI report:
* 8b4f68255a0a91f32757394d86405e46f60118c5 Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/142809001) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362364858
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -25,41 +25,41 @@ under the License.
* This will be replaced by the TOC
{:toc}
-SELECT queries are specified with the `sqlQuery()` method of the `TableEnvironment`. The method returns the result of the SELECT query as a `Table`. A `Table` can be used in [subsequent SQL and Table API queries]({{ site.baseurl }}/dev/table/common.html#mixing-table-api-and-sql), be [converted into a DataSet or DataStream]({{ site.baseurl }}/dev/table/common.html#integration-with-datastream-and-dataset-api), or [written to a TableSink]({{ site.baseurl }}/dev/table/common.html#emit-a-table). SQL and Table API queries can be seamlessly mixed and are holistically optimized and translated into a single program.
+SELECT 查询需要使用 `TableEnvironment` 的 `sqlQuery()` 方法加以指定。这个方法会以 `Table` 的形式返回 SELECT 的查询结果。 `Table` 可以被用于 [随后的SQL 与 Table API 查询]({{ site.baseurl }}/zh/dev/table/common.html#mixing-table-api-and-sql) 、 [转换为 DataSet 或 DataStream ]({{ site.baseurl }}/zh/dev/table/common.html#integration-with-datastream-and-dataset-api)或 [输出到 TableSink ]({{ site.baseurl }}/dev/table/common.html#emit-a-table))。SQL 与 Table API 的查询可以进行无缝融合、整体优化并翻译为单一的程序。
-In order to access a table in a SQL query, it must be [registered in the TableEnvironment]({{ site.baseurl }}/dev/table/common.html#register-tables-in-the-catalog). A table can be registered from a [TableSource]({{ site.baseurl }}/dev/table/common.html#register-a-tablesource), [Table]({{ site.baseurl }}/dev/table/common.html#register-a-table), [CREATE TABLE statement](#create-table), [DataStream, or DataSet]({{ site.baseurl }}/dev/table/common.html#register-a-datastream-or-dataset-as-table). Alternatively, users can also [register catalogs in a TableEnvironment]({{ site.baseurl }}/dev/table/catalogs.html) to specify the location of the data sources.
+为了可以在 SQL 查询中访问到表，你需要先 [在 TableEnvironment 中注册表 ]({{ site.baseurl }}/zh/dev/table/common.html#register-tables-in-the-catalog). 表可以通过 [TableSource]({{ site.baseurl }}/zh/dev/table/common.html#register-a-tablesource)、 [Table]({{ site.baseurl }}/zh/dev/table/common.html#register-a-table)、[CREATE TABLE 语句](create.html)、 [DataStream 或 DataSet]({{ site.baseurl }}/zh/dev/table/common.html#register-a-datastream-or-dataset-as-table) 注册。 用户也可以通过 [向 TableEnvironment 中注册 catalog ]({{ site.baseurl }}/zh/dev/table/catalogs.html) 的方式指定数据源的位置。
Review comment:
```suggestion
为了可以在 SQL 查询中访问到表，你需要先 [在 TableEnvironment 中注册表 ]({{ site.baseurl }}/zh/dev/table/common.html#register-tables-in-the-catalog)。表可以通过 [TableSource]({{ site.baseurl }}/zh/dev/table/common.html#register-a-tablesource)、 [Table]({{ site.baseurl }}/zh/dev/table/common.html#register-a-table)、[CREATE TABLE 语句](create.html)、 [DataStream 或 DataSet]({{ site.baseurl }}/zh/dev/table/common.html#register-a-datastream-or-dataset-as-table) 注册。 用户也可以通过 [向 TableEnvironment 中注册 catalog ]({{ site.baseurl }}/zh/dev/table/catalogs.html) 的方式指定数据源的位置。
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362367270
##########
File path: docs/dev/table/sql/queries.zh.md
##########
@@ -925,26 +923,26 @@ val result1 = tableEnv.sqlQuery(
</div>
</div>
-#### No Ranking Output Optimization
+#### 不进行排序输出的优化
-As described above, the `rownum` field will be written into the result table as one field of the unique key, which may lead to a lot of records being written to the result table. For example, when the record (say `product-1001`) of ranking 9 is updated and its rank is upgraded to 1, all the records from ranking 1 ~ 9 will be output to the result table as update messages. If the result table receives too many data, it will become the bottleneck of the SQL job.
+如上文所描述，`rownum` 字段会作为唯一键的其中一个字段写到结果表里面，这会导致大量的结构写出到结果表。比如，当原始结果（名为 `product-1001` ）从排序第九变化为排序第一时，排名 1-9 的所有结果都会以更新消息的形式发送到结果表。若结果表收到太多的数据，将会成为 SQL 任务的瓶颈。
Review comment:
```suggestion
如上文所描述，`rownum` 字段会作为唯一键的其中一个字段写到结果表里面，这会导致大量的结果写出到结果表。比如，当原始结果（名为 `product-1001` ）从排序第九变化为排序第一时，排名 1-9 的所有结果都会以更新消息的形式发送到结果表。若结果表收到太多的数据，将会成为 SQL 任务的瓶颈。
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot commented on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
flinkbot commented on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570070356
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.
## Automated Checks
Last check on commit 8b4f68255a0a91f32757394d86405e46f60118c5 (Wed Jan 01 17:40:40 UTC 2020)
✅no warnings
<sub>Mention the bot in a comment to re-run the automated checks.</sub>
## Review Progress
* ❓ 1. The [description] looks good.
* ❓ 2. There is [consensus] that the contribution should go into to Flink.
* ❓ 3. Needs [attention] from.
* ❓ 4. The change fits into the overall [architecture].
* ❓ 5. Overall code [quality] is good.
Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process.<details>
The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required <summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`)
- `@flinkbot approve all` to approve all aspects
- `@flinkbot approve-until architecture` to approve everything until `architecture`
- `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention
- `@flinkbot disapprove architecture` to remove an approval you gave earlier
</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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570073257
<!--
Meta data
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/142809001 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:PENDING URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
-->
## CI report:
* 8b4f68255a0a91f32757394d86405e46f60118c5 Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/142809001) Azure: [PENDING](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] wuchong commented on a change in pull request #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
wuchong commented on a change in pull request #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#discussion_r362363610
##########
File path: docs/dev/table/sql/alter.zh.md
##########
@@ -110,28 +110,28 @@ NewOrders
</div>
</div>
-## ALTER TABLE
+## 修改表
-* Rename Table
+* 重命名表
{% highlight sql %}
ALTER TABLE [catalog_name.][db_name.]table_name RENAME TO new_table_name
{% endhighlight %}
-Rename the given table name to another new table name.
+把原有的表名更改为新的表名。
-* Set or Alter Table Properties
+* 设置或修改表属性
{% highlight sql %}
ALTER TABLE [catalog_name.][db_name.]table_name SET (key1=val1, key2=val2, ...)
{% endhighlight %}
-Set one or more properties in the specified table. If a particular property is already set in the table, override the old value with the new one.
+为指定的表设置一个或多个属性。若个别属性已经存在于表中，则使用新的值覆盖旧的值。
-## ALTER DATABASE
+## 修改数据库
{% highlight sql %}
ALTER DATABASE [catalog_name.]db_name SET (key1=val1, key2=val2, ...)
{% endhighlight %}
-Set one or more properties in the specified database. If a particular property is already set in the database, override the old value with the new one.
\ No newline at end of file
+在数据库中设置一个或读个属性。若个别属性已经在数据库中设定，将会使用新值覆盖旧值。
Review comment:
```suggestion
在数据库中设置一个或多个属性。若个别属性已经在数据库中设定，将会使用新值覆盖旧值。
```
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #10738:
[FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
Posted by GitBox <gi...@apache.org>.
flinkbot edited a comment on issue #10738: [FLINK-15385][table][docs] Translate SQL section of Table API into Chinese
URL: https://github.com/apache/flink/pull/10738#issuecomment-570073257
<!--
Meta data
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/142809001 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:8b4f68255a0a91f32757394d86405e46f60118c5 Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023 TriggerType:PUSH TriggerID:8b4f68255a0a91f32757394d86405e46f60118c5
Hash:827c1dc7e424d9e89d5573fe5a466682271803f8 Status:SUCCESS URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4092 TriggerType:PUSH TriggerID:827c1dc7e424d9e89d5573fe5a466682271803f8
Hash:827c1dc7e424d9e89d5573fe5a466682271803f8 Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/143077633 TriggerType:PUSH TriggerID:827c1dc7e424d9e89d5573fe5a466682271803f8
Hash:f481f0acdc30b1445a4de94de7ba4f2293305cbb Status:PENDING URL:https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4094 TriggerType:PUSH TriggerID:f481f0acdc30b1445a4de94de7ba4f2293305cbb
Hash:f481f0acdc30b1445a4de94de7ba4f2293305cbb Status:SUCCESS URL:https://travis-ci.com/flink-ci/flink/builds/143085088 TriggerType:PUSH TriggerID:f481f0acdc30b1445a4de94de7ba4f2293305cbb
-->
## CI report:
* 8b4f68255a0a91f32757394d86405e46f60118c5 Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/142809001) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4023)
* 827c1dc7e424d9e89d5573fe5a466682271803f8 Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/143077633) Azure: [SUCCESS](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4092)
* f481f0acdc30b1445a4de94de7ba4f2293305cbb Travis: [SUCCESS](https://travis-ci.com/flink-ci/flink/builds/143085088) Azure: [PENDING](https://dev.azure.com/rmetzger/5bd3ef0a-4359-41af-abca-811b04098d2e/_build/results?buildId=4094)
<details>
<summary>Bot commands</summary>
The @flinkbot bot supports the following commands:
- `@flinkbot run travis` re-run the last Travis build
- `@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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services