libenchao commented on a change in pull request #10822:
[FLINK-15081][docs-zh]Translate "Concepts & Common API" page of Table…
URL: https://github.com/apache/flink/pull/10822#discussion_r382574407
##########
File path: docs/dev/table/common.zh.md
##########
@@ -22,28 +22,28 @@ specific language governing permissions and limitations
under the License.
-->
-The Table API and SQL are integrated in a joint API. The central concept of
this API is a `Table` which serves as input and output of queries. This
document shows the common structure of programs with Table API and SQL queries,
how to register a `Table`, how to query a `Table`, and how to emit a `Table`.
+Table API 和 SQL 集成在同一套 API 中。这套 API 的核心概念是`表（Table）`，用作查询的输入和输出。本文介绍了 Table
API 和 SQL 查询程序的通用结构、如何注册`表`、如何查询`表`以及如何发出`表`。
* This will be replaced by the TOC
{:toc}
-Main Differences Between the Two Planners
+两种计划器（Planner）的主要区别
-----------------------------------------
-1. Blink treats batch jobs as a special case of streaming. As such, the
conversion between Table and DataSet is also not supported, and batch jobs will
not be translated into `DateSet` programs but translated into `DataStream`
programs, the same as the streaming jobs.
-2. The Blink planner does not support `BatchTableSource`, use bounded
`StreamTableSource` instead of it.
-3. The Blink planner only support the brand new `Catalog` and does not support
`ExternalCatalog` which is deprecated.
-4. The implementations of `FilterableTableSource` for the old planner and the
Blink planner are incompatible. The old planner will push down
`PlannerExpression`s into `FilterableTableSource`, while the Blink planner will
push down `Expression`s.
-5. String based key-value config options (Please see the documentation about
[Configuration]({{ site.baseurl }}/dev/table/config.html) for details) are only
used for the Blink planner.
-6. The implementation(`CalciteConfig`) of `PlannerConfig` in two planners is
different.
-7. The Blink planner will optimize multiple-sinks into one DAG (supported only
on `TableEnvironment`, not on `StreamTableEnvironment`). The old planner will
always optimize each sink into a new DAG, where all DAGs are independent of
each other.
-8. The old planner does not support catalog statistics now, while the Blink
planner does.
+1. Blink
将批处理作业视作流处理的一种特例。严格来说，表和批数据之间的转换并不受支持，并且批处理作业也不会转换成`批处理`程序而是转换成流处理程序，`流处理`作业也一样。
+2. Blink 计划器不支持 `BatchTableSource`，而是使用有界的 `StreamTableSource` 来替代。
+3. Blink 计划器仅支持全新的 `Catalog` 并且不支持被弃用的 `ExternalCatalog`。
+4. 原版计划器和 Blink 计划器中 `FilterableTableSource` 的实现是不兼容的。原版计划器会将
`PlannerExpression` 下推至 `FilterableTableSource`，而 Blink 计划器则是将 `Expression` 下推。
+5. 基于字符串的键值配置选项仅在 Blink 计划器中使用。（详情参见 [配置]({{ site.baseurl
}}/zh/dev/table/config.html) ）
+6. `PlannerConfig` 在两种计划器中的实现（`CalciteConfig`）是不同的。
+7. Blink 计划器会将多sink（multiple-sinks）优化成一张有向无环图（DAG）（仅支持 `TableEnvironment`，不支持
`StreamTableEnvironment`）。原版计划器总是将每个sink都优化成一个新的有向无环图，且所有图相互独立。
+8. 原版计划器目前不支持 catalog 统计，而 Blink 支持。
Review comment:
”catalog 统计“ -> "catalog 统计信息” or 统计数据？
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
