lirui-apache commented on a change in pull request #11390:
[FLINK-16096][docs-zh] Translate dev/table/catalog.zh.md into Chinese
URL: https://github.com/apache/flink/pull/11390#discussion_r392770135
##########
File path: docs/dev/table/catalogs.zh.md
##########
@@ -22,44 +22,44 @@ specific language governing permissions and limitations
under the License.
-->
-Catalogs provide metadata, such as databases, tables, partitions, views, and
functions and information needed to access data stored in a database or other
external systems.
+目录提供了元数据信息，例如数据库、表、分区、视图以及数据库或其他外部系统中存储的函数和信息。
-One of the most crucial aspects of data processing is managing metadata.
-It may be transient metadata like temporary tables, or UDFs registered against
the table environment.
-Or permanent metadata, like that in a Hive Metastore. Catalogs provide a
unified API for managing metadata and making it accessible from the Table API
and SQL Queries.
+数据处理最关键的方面之一是管理元数据。
+目录可以是临时元数据，例如临时表、针对表环境注册的 UDF。
+它也可以是持久化的元数据，例如 Hive Metastore 中的元数据。目录提供了一个统一的API，用于管理元数据，并使其可以从 Table API 和
SQL 查询语句中来访问。
* This will be replaced by the TOC
{:toc}
-## Catalog Types
+## 目录 (catalog) 类型
-### GenericInMemoryCatalog
+### GenericInMemory 目录
-The `GenericInMemoryCatalog` is an in-memory implementation of a catalog. All
objects will be available only for the lifetime of the session.
+GenericInMemory 目录是内存中实现的目录，所有对象只在 session 的存活期内可用。
-### HiveCatalog
+### Hive 目录
-The `HiveCatalog` serves two purposes; as persistent storage for pure Flink
metadata, and as an interface for reading and writing existing Hive metadata.
-Flink's [Hive documentation]({{ site.baseurl }}/dev/table/hive/index.html)
provides full details on setting up the catalog and interfacing with an
existing Hive installation.
+`HiveCatalog` 服务有两个用途：作为原生 Flink 元数据的持久化存储，以及作为读写现有 Hive 目录的接口。
Review comment:
```suggestion
`HiveCatalog` 有两个用途：作为原生 Flink 元数据的持久化存储，以及作为读写现有 Hive 元数据的接口。
```
----------------------------------------------------------------
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
With regards,
Apache Git Services
