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_r382632936
##########
File path: docs/dev/table/common.zh.md
##########
@@ -288,53 +287,36 @@ b_b_t_env =
BatchTableEnvironment.create(environment_settings=b_b_settings)
</div>
</div>
-**Note:** If there is only one planner jar in `/lib` directory, you can use
`useAnyPlanner` (`use_any_planner` for python) to create specific
`EnvironmentSettings`.
+**注释：** 如果`/lib`目录中只有一中计划器的 jar 包，则可以使用`useAnyPlanner`（python 使用 `use
any_u_planner`）创建 `EnvironmentSettings`。
{% top %}
-Create Tables in the Catalog
+在 Catalog 中创建表
-------------------------------
-A `TableEnvironment` maintains a map of catalogs of tables which are created
with an identifier. Each
-identifier consists of 3 parts: catalog name, database name and object name.
If a catalog or database is not
-specified, the current default value will be used (see examples in the [Table
identifier expanding](#table-identifier-expanding) section).
+`TableEnvironment` 维护着一个由标识符（identifier）创建的表 catalog 的映射。标识符由三个部分组成：catalog
名称、数据库名称以及对象名称。如果 catalog
或者数据库没有指明，就会使用当前默认值（参见[表标识符扩展](#table-identifier-expanding)章节中的例子）。
-Tables can be either virtual (`VIEWS`) or regular (`TABLES`). `VIEWS` can be
created from an
-existing `Table` object, usually the result of a Table API or SQL query.
`TABLES` describe
-external data, such as a file, database table, or message queue.
+表可以使虚拟的（`视图（VIEW）`）也可以是常规的（`表（TABLES）`）。`视图`可以从已经存在的``表中创建，一般是 Tbale API 或者
SQL 的查询结果。`表`记录外部数据，例如文件、数据库表或者消息队列。
-### Temporary vs Permanent tables.
+### 零时表（Temporary Table）和永久表（Permanent Table）
-Tables may either be temporary, and tied to the lifecycle of a single Flink
session, or permanent,
-and visible across multiple Flink sessions and clusters.
+表可以是临时的，并与单个 Flink 会话（session）的生命周期相关，也可以是永久的，并且在多个 Flink 会话和群集（cluster）中可见。
-Permanent tables require a [catalog]({{ site.baseurl
}}/dev/table/catalogs.html) (such as Hive Metastore)
-to maintain metadata about the table. Once a permanent table is created, it is
visible to any Flink
-session that is connected to the catalog and will continue to exist until the
table is explicitly
-dropped.
+永久表需要 [catalog]({{ site.baseurl }}/zh/dev/table/catalogs.html)（例如 Hive
Metastore）以维护表的元数据。一旦永久表被创建，它将对任何连接到 catalog 的 Flink 会话可见且持续存在，直至表明确删除。
-On the other hand, temporary tables are always stored in memory and only exist
for the duration of
-the Flink session they are created within. These tables are not visible to
other sessions. They are
-not bound to any catalog or database but can be created in the namespace of
one. Temporary tables
-are not dropped if their corresponding database is removed.
+另一方面，零时表通常保存于内存中并且仅在创建它们的 Flink 会话持续期间存在。这些表对于其它会话是不可见的。它们不与任何 catalog
或者数据库绑定但可以在一个命名空间（namespace）中创建。即使它们对应的数据库被删除，零时表也不会被删除。
Review comment:
零时表
----------------------------------------------------------------
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
