leonardBang commented on a change in pull request #11909:
URL: https://github.com/apache/flink/pull/11909#discussion_r415191395
##########
File path: docs/dev/table/config.zh.md
##########
@@ -22,29 +22,22 @@ specific language governing permissions and limitations
under the License.
-->
-By default, the Table & SQL API is preconfigured for producing accurate
results with acceptable
-performance.
+默认情况下，Table & SQL API 已经预先配置，为了产生满足性能要求的准确结果。
-Depending on the requirements of a table program, it might be necessary to
adjust
-certain parameters for optimization. For example, unbounded streaming programs
may need to ensure
-that the required state size is capped (see [streaming
concepts](./streaming/query_configuration.html)).
+根据表程序的要求，可能需要调整特定的参数用于优化。例如，无界流程序可能需要保证所需的状态大小是有上限的(请参阅
[流式概念](./streaming/query_configuration.html)).
* This will be replaced by the TOC
{:toc}
-### Overview
+### 概览
-In every table environment, the `TableConfig` offers options for configuring
the current session.
+在每个Table环境中，`TableConfig` 提供了用于配置当前会话的选项。
-For common or important configuration options, the `TableConfig` provides
getters and setters methods
-with detailed inline documentation.
+对于常见或者重要的配置选项，`TableConfig` 提供了具有详细内联文档的`getters`和`setters`方法。
-For more advanced configuration, users can directly access the underlying
key-value map. The following
-sections list all available options that can be used to adjust Flink Table &
SQL API programs.
+对于更加高级的配置，用户可以直接访问基础键值对。以下各节列举了所有可用于调整 Flink Table & SQL API 程序的选项。
-<span class="label label-danger">Attention</span> Because options are read at
different point in time
-when performing operations, it is recommended to set configuration options
early after instantiating a
-table environment.
+<span class="label label-danger">注意</span>
因为在执行操作时，选项会在不同的时间点被读取，所以推荐在实例化Table环境后尽早地设置配置选项。
Review comment:
因为配置项会在执行操作的不同时间点被读取，所以推荐在实例化 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]
