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_r382625212
##########
File path: docs/dev/table/common.zh.md
##########
@@ -123,30 +123,29 @@ table_env.execute("python_job")
</div>
</div>
-**Note:** Table API and SQL queries can be easily integrated with and embedded
into DataStream or DataSet programs. Have a look at the [Integration with
DataStream and DataSet API](#integration-with-datastream-and-dataset-api)
section to learn how DataStreams and DataSets can be converted into Tables and
vice versa.
+**注释：** Table API 和 SQL 查询可以很容易地集成并嵌入到流处理或批处理程序中。 请参阅[与 DataStream 和 DataSet
API 结合](#integration-with-datastream-and-dataset-api) 章节了解如何将数据流和数据集与表之间的相互转化。
{% top %}
-Create a TableEnvironment
+创建 TableEnvironment
-------------------------
-The `TableEnvironment` is a central concept of the Table API and SQL
integration. It is responsible for:
+`TableEnvironment` 是 Table API 和 SQL 的核心概念。它负责:
-* Registering a `Table` in the internal catalog
-* Registering catalogs
-* Loading pluggable modules
-* Executing SQL queries
-* Registering a user-defined (scalar, table, or aggregation) function
-* Converting a `DataStream` or `DataSet` into a `Table`
-* Holding a reference to an `ExecutionEnvironment` or
`StreamExecutionEnvironment`
+* 在内部的 catalog 中注册`表`
+* 注册外部的 catalog
+* 执行 SQL 查询
+* 注册自定义函数 （scalar、table 或 aggregation）
+* 将`流数据集`或`批数据集`转换成`表`
+* 引用 `ExecutionEnvironment` 或 `StreamExecutionEnvironment`
-A `Table` is always bound to a specific `TableEnvironment`. It is not possible
to combine tables of different TableEnvironments in the same query, e.g., to
join or union them.
+`表`总是与确定的 `TableEnvironment` 绑定。不能在同一条查询中使用不同 TableEnvironment 中的表，例如，对它们进行
join 或 union 操作。
Review comment:
确定的 `TableEnvironment` -> 特定的`TableEnvironment` or 某个特定的
`TableEnvironment`
----------------------------------------------------------------
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
