klion26 commented on a change in pull request #12420:
URL: https://github.com/apache/flink/pull/12420#discussion_r451970665
##########
File path: docs/dev/table/streaming/joins.zh.md
##########
@@ -300,25 +285,26 @@ FROM
ON r.currency = o.currency
{% endhighlight %}
-Each record from the probe side will be joined with the current version of the
build side table. In our example, the query is using the processing-time
notion, so a newly appended order would always be joined with the most recent
version of `LatestRates` when executing the operation. Note that the result is
not deterministic for processing-time.
+探针侧表中的每个记录都将与构建侧表的当前版本所关联。 在此示例中，查询使用 `processing-time` 作为处理时间，因而新增订单将始终与表
`LatestRates` 的最新汇率执行 Join 操作。 注意，结果对于处理时间来说不是确定的。
+
+与[常规 Join](#regular-joins) 相比，尽管构建侧表的数据发生了变化，但时态表 Join 的变化前结果不会随之变化。而且时态表 Join
运算非常轻量级且不会保留任何状态。
-In contrast to [regular joins](#regular-joins), the previous results of the
temporal table join will not be affected despite the changes on the build side.
Also, the temporal table join operator is very lightweight and does not keep
any state.
+与[时间区间 Join](#interval-joins) 相比，时态表 Join 没有定义决定哪些记录将被 Join 的时间窗口。
+探针侧的记录将总是与构建侧在对应 `processing time` 时间的最新数据执行 Join。因而构建侧的数据可能是任意旧的。
-Compared to [interval joins](#interval-joins), temporal table joins do not
define a time window within which the records will be joined.
-Records from the probe side are always joined with the build side's latest
version at processing time. Thus, records on the build side might be
arbitrarily old.
+[时态表函数 Join](#join-with-a-temporal-table-function) 和时态表 Join都有类似的功能，但是有不同的 SQL
语法和 runtime 实现：
Review comment:
```suggestion
[时态表函数 Join](#join-with-a-temporal-table-function) 和时态表 Join 都有类似的功能，但是有不同的
SQL 语法和 runtime 实现：
```
##########
File path: docs/dev/table/streaming/joins.zh.md
##########
@@ -327,10 +313,10 @@ FROM table1 [AS <alias1>]
ON table1.column-name1 = table2.column-name1
{% endhighlight %}
-Currently, only support INNER JOIN and LEFT JOIN. The `FOR SYSTEM_TIME AS OF
table1.proctime` should be followed after temporal table. `proctime` is a
[processing time attribute](time_attributes.html#processing-time) of `table1`.
-This means that it takes a snapshot of the temporal table at processing time
when joining every record from left table.
+目前只支持 INNER JOIN 和 LEFT JOIN，`FOR SYSTEM_TIME AS OF table1.proctime` 应位于时态表之后.
`proctime` 是 `table1` 的 [processing time 属性]({%link
dev/table/streaming/time_attributes.zh.md %}#processing-time)。
Review comment:
这里的链接 `{%link dev/table/streaming/time_attributes.zh.md
%}#processing-time` 有问题，不是这个文档的问题，而是要在
`dev/table/streaming/time_attributes.zh.md` 这个文件的对应标题前面添加 锚点（具体可以参考
[wiki](https://cwiki.apache.org/confluence/display/FLINK/Flink+Translation+Specifications))，这个可以单独提一个
hotfix PR
##########
File path: docs/dev/table/streaming/joins.zh.md
##########
@@ -300,25 +285,26 @@ FROM
ON r.currency = o.currency
{% endhighlight %}
-Each record from the probe side will be joined with the current version of the
build side table. In our example, the query is using the processing-time
notion, so a newly appended order would always be joined with the most recent
version of `LatestRates` when executing the operation. Note that the result is
not deterministic for processing-time.
+探针侧表中的每个记录都将与构建侧表的当前版本所关联。 在此示例中，查询使用 `processing-time` 作为处理时间，因而新增订单将始终与表
`LatestRates` 的最新汇率执行 Join 操作。 注意，结果对于处理时间来说不是确定的。
Review comment:
这里的 processing-time 和 event-time 能否都翻译一下呢？翻译的话整篇文章的都进行一下翻译
因为 [时间属性](http://localhost:4000/zh/dev/table/streaming/time_attributes.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:
us...@infra.apache.org
