RocMarshal commented on a change in pull request #16865:
URL: https://github.com/apache/flink/pull/16865#discussion_r701835938
##########
File path:
docs/content.zh/docs/dev/datastream/execution/execution_configuration.md
##########
@@ -45,46 +45,45 @@ var executionConfig = env.getConfig
{{< /tab >}}
{{< /tabs >}}
-The following configuration options are available: (the default is bold)
+以下是可用的配置选项：（默认为粗体）
-- `setClosureCleanerLevel()`. The closure cleaner level is set to
`ClosureCleanerLevel.RECURSIVE` by default. The closure cleaner removes
unneeded references to the surrounding class of anonymous functions inside
Flink programs.
-With the closure cleaner disabled, it might happen that an anonymous user
function is referencing the surrounding class, which is usually not
Serializable. This will lead to exceptions by the serializer. The settings are:
-`NONE`: disable the closure cleaner completely, `TOP_LEVEL`: clean only the
top-level class without recursing into fields, `RECURSIVE`: clean all the
fields recursively.
+- `setClosureCleanerLevel()`。closure cleaner 的级别默认设置为
`ClosureCleanerLevel.RECURSIVE`。closure cleaner 删除 Flink 程序中对匿名 function
的调用类的不必要引用。禁用 closure cleaner 后，用户的匿名 function
可能正引用一些不可序列化的调用类。这将导致序列化器出现异常。可设置的值是：
+`NONE`：完全禁用 closure cleaner ，`TOP_LEVEL`：只清理顶级类而不递归到字段中，`RECURSIVE`：递归清理所有字段。
-- `getParallelism()` / `setParallelism(int parallelism)` Set the default
parallelism for the job.
+- `getParallelism()` / `setParallelism(int parallelism)`。为作业设置默认的并行度。
-- `getMaxParallelism()` / `setMaxParallelism(int parallelism)` Set the default
maximum parallelism for the job. This setting determines the maximum degree of
parallelism and specifies the upper limit for dynamic scaling.
+- `getMaxParallelism()` / `setMaxParallelism(int
parallelism)`。为作业设置默认的最大并行度。此设置决定最大并行度并指定动态缩放的上限。
-- `getNumberOfExecutionRetries()` / `setNumberOfExecutionRetries(int
numberOfExecutionRetries)` Sets the number of times that failed tasks are
re-executed. A value of zero effectively disables fault tolerance. A value of
`-1` indicates that the system default value (as defined in the configuration)
should be used. This is deprecated, use [restart strategies]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) instead.
+- `getNumberOfExecutionRetries()` / `setNumberOfExecutionRetries(int
numberOfExecutionRetries)`。设置失败任务重新执行的次数。值为零会有效地禁用容错。`-1`
表示使用系统默认值（在配置中定义）。该配置已弃用，请改用[重启策略]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) 。
-- `getExecutionRetryDelay()` / `setExecutionRetryDelay(long
executionRetryDelay)` Sets the delay in milliseconds that the system waits
after a job has failed, before re-executing it. The delay starts after all
tasks have been successfully stopped on the TaskManagers, and once the delay is
past, the tasks are re-started. This parameter is useful to delay re-execution
in order to let certain time-out related failures surface fully (like broken
connections that have not fully timed out), before attempting a re-execution
and immediately failing again due to the same problem. This parameter only has
an effect if the number of execution re-tries is one or more. This is
deprecated, use [restart strategies]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) instead.
+- `getExecutionRetryDelay()` / `setExecutionRetryDelay(long
executionRetryDelay)`。设置系统在作业失败后重新执行之前等待的延迟（以毫秒为单位）。在 TaskManagers
上成功停止所有任务后，开始计算延迟，一旦延迟过去，任务会被重新启动。此参数对于延迟重新执行很有用，以便在尝试重新执行并由于相同的问题立即再次失败之前，让某些超时相关的故障完全浮出水面（例如尚未完全超时的断开连接）。此参数仅在执行重试次数为一次或多次时有效。该配置已被弃用，请改用[重启策略]({{<
ref "docs/ops/state/task_failure_recovery" >}}#restart-strategies) 。
-- `getExecutionMode()` / `setExecutionMode()`. The default execution mode is
PIPELINED. Sets the execution mode to execute the program. The execution mode
defines whether data exchanges are performed in a batch or on a pipelined
manner.
+- `getExecutionMode()` / `setExecutionMode()`。默认的执行模式是
PIPELINED。设置执行模式以执行程序。执行模式定义了数据交换是以批处理方式还是以流方式执行。
-- `enableForceKryo()` / **`disableForceKryo`**. Kryo is not forced by default.
Forces the GenericTypeInformation to use the Kryo serializer for POJOs even
though we could analyze them as a POJO. In some cases this might be preferable.
For example, when Flink's internal serializers fail to handle a POJO properly.
+- `enableForceKryo()` / **`disableForceKryo`**。默认情况下不强制使用 Kryo。强制
GenericTypeInformation 对 POJO 使用 Kryo 序列化器，即使我们可以将它们作为 POJO
进行分析。在某些情况下，这可能更可取。例如，当 Flink 的内部序列化器无法正确处理 POJO 时。
-- `enableForceAvro()` / **`disableForceAvro()`**. Avro is not forced by
default. Forces the Flink AvroTypeInfo to use the Avro serializer instead of
Kryo for serializing Avro POJOs.
+- `enableForceAvro()` / **`disableForceAvro()`**。默认情况下不强制使用 Avro。强制 Flink
AvroTypeInfo 使用 Avro 序列化器而不是 Kryo 来序列化 Avro 的 POJO。
-- `enableObjectReuse()` / **`disableObjectReuse()`** By default, objects are
not reused in Flink. Enabling the object reuse mode will instruct the runtime
to reuse user objects for better performance. Keep in mind that this can lead
to bugs when the user-code function of an operation is not aware of this
behavior.
+- `enableObjectReuse()` / **`disableObjectReuse()`**。默认情况下，Flink
中不重用对象。启用对象重用模式会指示运行时重用用户对象以获得更好的性能。请记住，当一个算子的用户代码 function 没有意识到这种行为时可能会导致bug。
-- `getGlobalJobParameters()` / `setGlobalJobParameters()` This method allows
users to set custom objects as a global configuration for the job. Since the
`ExecutionConfig` is accessible in all user defined functions, this is an easy
method for making configuration globally available in a job.
+- `getGlobalJobParameters()` /
`setGlobalJobParameters()`。此方法允许用户将自定义对象设置为作业的全局配置。由于 `ExecutionConfig`
可在所有用户定义的 function 中访问，因此这是一种使配置在作业中全局可用的简单方法。
-- `addDefaultKryoSerializer(Class<?> type, Serializer<?> serializer)` Register
a Kryo serializer instance for the given `type`.
+- `addDefaultKryoSerializer(Class<?> type, Serializer<?> serializer)`。为指定的类型注册
Kryo 序列化器实例。
-- `addDefaultKryoSerializer(Class<?> type, Class<? extends Serializer<?>>
serializerClass)` Register a Kryo serializer class for the given `type`.
+- `addDefaultKryoSerializer(Class<?> type, Class<? extends Serializer<?>>
serializerClass)`。为指定的类型注册 Kryo 序列化器的类。
-- `registerTypeWithKryoSerializer(Class<?> type, Serializer<?> serializer)`
Register the given type with Kryo and specify a serializer for it. By
registering a type with Kryo, the serialization of the type will be much more
efficient.
+- `registerTypeWithKryoSerializer(Class<?> type, Serializer<?> serializer)`。使用
Kryo 注册指定类型并为其指定序列化器。通过使用 Kryo 注册类型，该类型的序列化将更加高效。
-- `registerKryoType(Class<?> type)` If the type ends up being serialized with
Kryo, then it will be registered at Kryo to make sure that only tags (integer
IDs) are written. If a type is not registered with Kryo, its entire class-name
will be serialized with every instance, leading to much higher I/O costs.
+- `registerKryoType(Class<?> type)`。如果类型最终被 Kryo 序列化，那么它将在 Kryo 中注册，以确保只有标记（整数
ID）被写入。如果一个类型没有在 Kryo 注册，它的全限定类名将在每个实例中被序列化，从而导致更高的 I/O 成本。
Review comment:
```suggestion
- `registerKryoType(Class<?> type)`。如果类型最终被 Kryo 序列化，那么它将在 Kryo
中注册，以确保只有标记（整数 ID）被写入。如果一个类型没有在 Kryo 注册，它的全限定类名将在每个实例中被序列化，从而导致更高的 I/O 成本。
```
##########
File path:
docs/content.zh/docs/dev/datastream/execution/execution_configuration.md
##########
@@ -45,46 +45,45 @@ var executionConfig = env.getConfig
{{< /tab >}}
{{< /tabs >}}
-The following configuration options are available: (the default is bold)
+以下是可用的配置选项：（默认为粗体）
-- `setClosureCleanerLevel()`. The closure cleaner level is set to
`ClosureCleanerLevel.RECURSIVE` by default. The closure cleaner removes
unneeded references to the surrounding class of anonymous functions inside
Flink programs.
-With the closure cleaner disabled, it might happen that an anonymous user
function is referencing the surrounding class, which is usually not
Serializable. This will lead to exceptions by the serializer. The settings are:
-`NONE`: disable the closure cleaner completely, `TOP_LEVEL`: clean only the
top-level class without recursing into fields, `RECURSIVE`: clean all the
fields recursively.
+- `setClosureCleanerLevel()`。closure cleaner 的级别默认设置为
`ClosureCleanerLevel.RECURSIVE`。closure cleaner 删除 Flink 程序中对匿名 function
的调用类的不必要引用。禁用 closure cleaner 后，用户的匿名 function
可能正引用一些不可序列化的调用类。这将导致序列化器出现异常。可设置的值是：
+`NONE`：完全禁用 closure cleaner ，`TOP_LEVEL`：只清理顶级类而不递归到字段中，`RECURSIVE`：递归清理所有字段。
-- `getParallelism()` / `setParallelism(int parallelism)` Set the default
parallelism for the job.
+- `getParallelism()` / `setParallelism(int parallelism)`。为作业设置默认的并行度。
-- `getMaxParallelism()` / `setMaxParallelism(int parallelism)` Set the default
maximum parallelism for the job. This setting determines the maximum degree of
parallelism and specifies the upper limit for dynamic scaling.
+- `getMaxParallelism()` / `setMaxParallelism(int
parallelism)`。为作业设置默认的最大并行度。此设置决定最大并行度并指定动态缩放的上限。
-- `getNumberOfExecutionRetries()` / `setNumberOfExecutionRetries(int
numberOfExecutionRetries)` Sets the number of times that failed tasks are
re-executed. A value of zero effectively disables fault tolerance. A value of
`-1` indicates that the system default value (as defined in the configuration)
should be used. This is deprecated, use [restart strategies]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) instead.
+- `getNumberOfExecutionRetries()` / `setNumberOfExecutionRetries(int
numberOfExecutionRetries)`。设置失败任务重新执行的次数。值为零会有效地禁用容错。`-1`
表示使用系统默认值（在配置中定义）。该配置已弃用，请改用[重启策略]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) 。
-- `getExecutionRetryDelay()` / `setExecutionRetryDelay(long
executionRetryDelay)` Sets the delay in milliseconds that the system waits
after a job has failed, before re-executing it. The delay starts after all
tasks have been successfully stopped on the TaskManagers, and once the delay is
past, the tasks are re-started. This parameter is useful to delay re-execution
in order to let certain time-out related failures surface fully (like broken
connections that have not fully timed out), before attempting a re-execution
and immediately failing again due to the same problem. This parameter only has
an effect if the number of execution re-tries is one or more. This is
deprecated, use [restart strategies]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) instead.
+- `getExecutionRetryDelay()` / `setExecutionRetryDelay(long
executionRetryDelay)`。设置系统在作业失败后重新执行之前等待的延迟（以毫秒为单位）。在 TaskManagers
上成功停止所有任务后，开始计算延迟，一旦延迟过去，任务会被重新启动。此参数对于延迟重新执行很有用，以便在尝试重新执行并由于相同的问题立即再次失败之前，让某些超时相关的故障完全浮出水面（例如尚未完全超时的断开连接）。此参数仅在执行重试次数为一次或多次时有效。该配置已被弃用，请改用[重启策略]({{<
ref "docs/ops/state/task_failure_recovery" >}}#restart-strategies) 。
-- `getExecutionMode()` / `setExecutionMode()`. The default execution mode is
PIPELINED. Sets the execution mode to execute the program. The execution mode
defines whether data exchanges are performed in a batch or on a pipelined
manner.
+- `getExecutionMode()` / `setExecutionMode()`。默认的执行模式是
PIPELINED。设置执行模式以执行程序。执行模式定义了数据交换是以批处理方式还是以流方式执行。
-- `enableForceKryo()` / **`disableForceKryo`**. Kryo is not forced by default.
Forces the GenericTypeInformation to use the Kryo serializer for POJOs even
though we could analyze them as a POJO. In some cases this might be preferable.
For example, when Flink's internal serializers fail to handle a POJO properly.
+- `enableForceKryo()` / **`disableForceKryo`**。默认情况下不强制使用 Kryo。强制
GenericTypeInformation 对 POJO 使用 Kryo 序列化器，即使我们可以将它们作为 POJO
进行分析。在某些情况下，这可能更可取。例如，当 Flink 的内部序列化器无法正确处理 POJO 时。
Review comment:
```suggestion
- `enableForceKryo()` / **`disableForceKryo`**。默认情况下不强制使用 Kryo。强制
GenericTypeInformation 对 POJO 使用 Kryo 序列化器，即使我们可以将它们作为 POJO
进行分析。在某些情况下，此配置可能被优先启用。例如，当 Flink 的内部序列化器无法正确处理 POJO 时。
```
Only a minor comment. Please let me know what's your opinion.
##########
File path:
docs/content.zh/docs/dev/datastream/execution/execution_configuration.md
##########
@@ -45,46 +45,45 @@ var executionConfig = env.getConfig
{{< /tab >}}
{{< /tabs >}}
-The following configuration options are available: (the default is bold)
+以下是可用的配置选项：（默认为粗体）
-- `setClosureCleanerLevel()`. The closure cleaner level is set to
`ClosureCleanerLevel.RECURSIVE` by default. The closure cleaner removes
unneeded references to the surrounding class of anonymous functions inside
Flink programs.
-With the closure cleaner disabled, it might happen that an anonymous user
function is referencing the surrounding class, which is usually not
Serializable. This will lead to exceptions by the serializer. The settings are:
-`NONE`: disable the closure cleaner completely, `TOP_LEVEL`: clean only the
top-level class without recursing into fields, `RECURSIVE`: clean all the
fields recursively.
+- `setClosureCleanerLevel()`。closure cleaner 的级别默认设置为
`ClosureCleanerLevel.RECURSIVE`。closure cleaner 删除 Flink 程序中对匿名 function
的调用类的不必要引用。禁用 closure cleaner 后，用户的匿名 function
可能正引用一些不可序列化的调用类。这将导致序列化器出现异常。可设置的值是：
+`NONE`：完全禁用 closure cleaner ，`TOP_LEVEL`：只清理顶级类而不递归到字段中，`RECURSIVE`：递归清理所有字段。
-- `getParallelism()` / `setParallelism(int parallelism)` Set the default
parallelism for the job.
+- `getParallelism()` / `setParallelism(int parallelism)`。为作业设置默认的并行度。
-- `getMaxParallelism()` / `setMaxParallelism(int parallelism)` Set the default
maximum parallelism for the job. This setting determines the maximum degree of
parallelism and specifies the upper limit for dynamic scaling.
+- `getMaxParallelism()` / `setMaxParallelism(int
parallelism)`。为作业设置默认的最大并行度。此设置决定最大并行度并指定动态缩放的上限。
-- `getNumberOfExecutionRetries()` / `setNumberOfExecutionRetries(int
numberOfExecutionRetries)` Sets the number of times that failed tasks are
re-executed. A value of zero effectively disables fault tolerance. A value of
`-1` indicates that the system default value (as defined in the configuration)
should be used. This is deprecated, use [restart strategies]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) instead.
+- `getNumberOfExecutionRetries()` / `setNumberOfExecutionRetries(int
numberOfExecutionRetries)`。设置失败任务重新执行的次数。值为零会有效地禁用容错。`-1`
表示使用系统默认值（在配置中定义）。该配置已弃用，请改用[重启策略]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) 。
-- `getExecutionRetryDelay()` / `setExecutionRetryDelay(long
executionRetryDelay)` Sets the delay in milliseconds that the system waits
after a job has failed, before re-executing it. The delay starts after all
tasks have been successfully stopped on the TaskManagers, and once the delay is
past, the tasks are re-started. This parameter is useful to delay re-execution
in order to let certain time-out related failures surface fully (like broken
connections that have not fully timed out), before attempting a re-execution
and immediately failing again due to the same problem. This parameter only has
an effect if the number of execution re-tries is one or more. This is
deprecated, use [restart strategies]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) instead.
+- `getExecutionRetryDelay()` / `setExecutionRetryDelay(long
executionRetryDelay)`。设置系统在作业失败后重新执行之前等待的延迟（以毫秒为单位）。在 TaskManagers
上成功停止所有任务后，开始计算延迟，一旦延迟过去，任务会被重新启动。此参数对于延迟重新执行很有用，以便在尝试重新执行并由于相同的问题立即再次失败之前，让某些超时相关的故障完全浮出水面（例如尚未完全超时的断开连接）。此参数仅在执行重试次数为一次或多次时有效。该配置已被弃用，请改用[重启策略]({{<
ref "docs/ops/state/task_failure_recovery" >}}#restart-strategies) 。
Review comment:
`以便在尝试重新执行并由于相同的问题立即再次失败之前`.
Maybe you could translate it in a better way.
##########
File path:
docs/content.zh/docs/dev/datastream/execution/execution_configuration.md
##########
@@ -45,46 +45,45 @@ var executionConfig = env.getConfig
{{< /tab >}}
{{< /tabs >}}
-The following configuration options are available: (the default is bold)
+以下是可用的配置选项：（默认为粗体）
-- `setClosureCleanerLevel()`. The closure cleaner level is set to
`ClosureCleanerLevel.RECURSIVE` by default. The closure cleaner removes
unneeded references to the surrounding class of anonymous functions inside
Flink programs.
-With the closure cleaner disabled, it might happen that an anonymous user
function is referencing the surrounding class, which is usually not
Serializable. This will lead to exceptions by the serializer. The settings are:
-`NONE`: disable the closure cleaner completely, `TOP_LEVEL`: clean only the
top-level class without recursing into fields, `RECURSIVE`: clean all the
fields recursively.
+- `setClosureCleanerLevel()`。closure cleaner 的级别默认设置为
`ClosureCleanerLevel.RECURSIVE`。closure cleaner 删除 Flink 程序中对匿名 function
的调用类的不必要引用。禁用 closure cleaner 后，用户的匿名 function
可能正引用一些不可序列化的调用类。这将导致序列化器出现异常。可设置的值是：
+`NONE`：完全禁用 closure cleaner ，`TOP_LEVEL`：只清理顶级类而不递归到字段中，`RECURSIVE`：递归清理所有字段。
-- `getParallelism()` / `setParallelism(int parallelism)` Set the default
parallelism for the job.
+- `getParallelism()` / `setParallelism(int parallelism)`。为作业设置默认的并行度。
-- `getMaxParallelism()` / `setMaxParallelism(int parallelism)` Set the default
maximum parallelism for the job. This setting determines the maximum degree of
parallelism and specifies the upper limit for dynamic scaling.
+- `getMaxParallelism()` / `setMaxParallelism(int
parallelism)`。为作业设置默认的最大并行度。此设置决定最大并行度并指定动态缩放的上限。
-- `getNumberOfExecutionRetries()` / `setNumberOfExecutionRetries(int
numberOfExecutionRetries)` Sets the number of times that failed tasks are
re-executed. A value of zero effectively disables fault tolerance. A value of
`-1` indicates that the system default value (as defined in the configuration)
should be used. This is deprecated, use [restart strategies]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) instead.
+- `getNumberOfExecutionRetries()` / `setNumberOfExecutionRetries(int
numberOfExecutionRetries)`。设置失败任务重新执行的次数。值为零会有效地禁用容错。`-1`
表示使用系统默认值（在配置中定义）。该配置已弃用，请改用[重启策略]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) 。
-- `getExecutionRetryDelay()` / `setExecutionRetryDelay(long
executionRetryDelay)` Sets the delay in milliseconds that the system waits
after a job has failed, before re-executing it. The delay starts after all
tasks have been successfully stopped on the TaskManagers, and once the delay is
past, the tasks are re-started. This parameter is useful to delay re-execution
in order to let certain time-out related failures surface fully (like broken
connections that have not fully timed out), before attempting a re-execution
and immediately failing again due to the same problem. This parameter only has
an effect if the number of execution re-tries is one or more. This is
deprecated, use [restart strategies]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) instead.
+- `getExecutionRetryDelay()` / `setExecutionRetryDelay(long
executionRetryDelay)`。设置系统在作业失败后重新执行之前等待的延迟（以毫秒为单位）。在 TaskManagers
上成功停止所有任务后，开始计算延迟，一旦延迟过去，任务会被重新启动。此参数对于延迟重新执行很有用，以便在尝试重新执行并由于相同的问题立即再次失败之前，让某些超时相关的故障完全浮出水面（例如尚未完全超时的断开连接）。此参数仅在执行重试次数为一次或多次时有效。该配置已被弃用，请改用[重启策略]({{<
ref "docs/ops/state/task_failure_recovery" >}}#restart-strategies) 。
-- `getExecutionMode()` / `setExecutionMode()`. The default execution mode is
PIPELINED. Sets the execution mode to execute the program. The execution mode
defines whether data exchanges are performed in a batch or on a pipelined
manner.
+- `getExecutionMode()` / `setExecutionMode()`。默认的执行模式是
PIPELINED。设置执行模式以执行程序。执行模式定义了数据交换是以批处理方式还是以流方式执行。
-- `enableForceKryo()` / **`disableForceKryo`**. Kryo is not forced by default.
Forces the GenericTypeInformation to use the Kryo serializer for POJOs even
though we could analyze them as a POJO. In some cases this might be preferable.
For example, when Flink's internal serializers fail to handle a POJO properly.
+- `enableForceKryo()` / **`disableForceKryo`**。默认情况下不强制使用 Kryo。强制
GenericTypeInformation 对 POJO 使用 Kryo 序列化器，即使我们可以将它们作为 POJO
进行分析。在某些情况下，这可能更可取。例如，当 Flink 的内部序列化器无法正确处理 POJO 时。
-- `enableForceAvro()` / **`disableForceAvro()`**. Avro is not forced by
default. Forces the Flink AvroTypeInfo to use the Avro serializer instead of
Kryo for serializing Avro POJOs.
+- `enableForceAvro()` / **`disableForceAvro()`**。默认情况下不强制使用 Avro。强制 Flink
AvroTypeInfo 使用 Avro 序列化器而不是 Kryo 来序列化 Avro 的 POJO。
-- `enableObjectReuse()` / **`disableObjectReuse()`** By default, objects are
not reused in Flink. Enabling the object reuse mode will instruct the runtime
to reuse user objects for better performance. Keep in mind that this can lead
to bugs when the user-code function of an operation is not aware of this
behavior.
+- `enableObjectReuse()` / **`disableObjectReuse()`**。默认情况下，Flink
中不重用对象。启用对象重用模式会指示运行时重用用户对象以获得更好的性能。请记住，当一个算子的用户代码 function 没有意识到这种行为时可能会导致bug。
-- `getGlobalJobParameters()` / `setGlobalJobParameters()` This method allows
users to set custom objects as a global configuration for the job. Since the
`ExecutionConfig` is accessible in all user defined functions, this is an easy
method for making configuration globally available in a job.
+- `getGlobalJobParameters()` /
`setGlobalJobParameters()`。此方法允许用户将自定义对象设置为作业的全局配置。由于 `ExecutionConfig`
可在所有用户定义的 function 中访问，因此这是一种使配置在作业中全局可用的简单方法。
-- `addDefaultKryoSerializer(Class<?> type, Serializer<?> serializer)` Register
a Kryo serializer instance for the given `type`.
+- `addDefaultKryoSerializer(Class<?> type, Serializer<?> serializer)`。为指定的类型注册
Kryo 序列化器实例。
-- `addDefaultKryoSerializer(Class<?> type, Class<? extends Serializer<?>>
serializerClass)` Register a Kryo serializer class for the given `type`.
+- `addDefaultKryoSerializer(Class<?> type, Class<? extends Serializer<?>>
serializerClass)`。为指定的类型注册 Kryo 序列化器的类。
-- `registerTypeWithKryoSerializer(Class<?> type, Serializer<?> serializer)`
Register the given type with Kryo and specify a serializer for it. By
registering a type with Kryo, the serialization of the type will be much more
efficient.
+- `registerTypeWithKryoSerializer(Class<?> type, Serializer<?> serializer)`。使用
Kryo 注册指定类型并为其指定序列化器。通过使用 Kryo 注册类型，该类型的序列化将更加高效。
-- `registerKryoType(Class<?> type)` If the type ends up being serialized with
Kryo, then it will be registered at Kryo to make sure that only tags (integer
IDs) are written. If a type is not registered with Kryo, its entire class-name
will be serialized with every instance, leading to much higher I/O costs.
+- `registerKryoType(Class<?> type)`。如果类型最终被 Kryo 序列化，那么它将在 Kryo 中注册，以确保只有标记（整数
ID）被写入。如果一个类型没有在 Kryo 注册，它的全限定类名将在每个实例中被序列化，从而导致更高的 I/O 成本。
-- `registerPojoType(Class<?> type)` Registers the given type with the
serialization stack. If the type is eventually serialized as a POJO, then the
type is registered with the POJO serializer. If the type ends up being
serialized with Kryo, then it will be registered at Kryo to make sure that only
tags are written. If a type is not registered with Kryo, its entire class-name
will be serialized with every instance, leading to much higher I/O costs.
+- `registerPojoType(Class<?> type)`。将指定的类型注册到序列化栈中。如果该类型最终被序列化为 POJO，那么该类型将注册到
POJO 序列化器中。如果该类型最终被 Kryo 序列化，那么它将在 Kryo 中注册，以确保只有标记被写入。如果一个类型没有在 Kryo
注册，它的全限定类名将在每个实例中被序列化，从而导致更高的I/O成本。
-Note that types registered with `registerKryoType()` are not available to
Flink's POJO serializer instance.
+注意：用 `registerKryoType()` 注册的类型对 Flink 的 Kryo 序列化器实例来说是不可用的。
-- `disableAutoTypeRegistration()` Automatic type registration is enabled by
default. The automatic type registration is registering all types (including
sub-types) used by usercode with Kryo and the POJO serializer.
+-
`disableAutoTypeRegistration()`。自动类型注册在默认情况下是启用的。自动类型注册是将用户代码使用的所有类型（包括子类型）注册到
Kryo 和 POJO 序列化器。
-- `setTaskCancellationInterval(long interval)` Sets the interval (in
milliseconds) to wait between consecutive attempts to cancel a running task.
When a task is canceled a new thread is created which periodically calls
`interrupt()` on the task thread, if the task thread does not terminate within
a certain time. This parameter refers to the time between consecutive calls to
`interrupt()` and is set by default to **30000** milliseconds, or **30
seconds**.
+- `setTaskCancellationInterval(long
interval)`。设置尝试连续取消正在运行任务的等待时间间隔（以毫秒为单位）。当一个任务被取消时，会创建一个新的线程，如果任务线程在一定时间内没有终止，新线程就会定期调用任务线程上的
`interrupt()` 。这个参数是指连续调用 `interrupt()` 的时间间隔，默认设置为 **30000** 毫秒，或 **30秒** 。
Review comment:
```suggestion
- `setTaskCancellationInterval(long
interval)`。设置尝试连续取消正在运行任务的等待时间间隔（以毫秒为单位）。当一个任务被取消时，会创建一个新的线程，如果任务线程在一定时间内没有终止，新线程就会定期调用任务线程上的
`interrupt()` 方法。这个参数是指连续调用 `interrupt()` 的时间间隔，默认设置为 **30000** 毫秒，或 **30秒** 。
```
##########
File path:
docs/content.zh/docs/dev/datastream/execution/execution_configuration.md
##########
@@ -45,46 +45,45 @@ var executionConfig = env.getConfig
{{< /tab >}}
{{< /tabs >}}
-The following configuration options are available: (the default is bold)
+以下是可用的配置选项：（默认为粗体）
-- `setClosureCleanerLevel()`. The closure cleaner level is set to
`ClosureCleanerLevel.RECURSIVE` by default. The closure cleaner removes
unneeded references to the surrounding class of anonymous functions inside
Flink programs.
-With the closure cleaner disabled, it might happen that an anonymous user
function is referencing the surrounding class, which is usually not
Serializable. This will lead to exceptions by the serializer. The settings are:
-`NONE`: disable the closure cleaner completely, `TOP_LEVEL`: clean only the
top-level class without recursing into fields, `RECURSIVE`: clean all the
fields recursively.
+- `setClosureCleanerLevel()`。closure cleaner 的级别默认设置为
`ClosureCleanerLevel.RECURSIVE`。closure cleaner 删除 Flink 程序中对匿名 function
的调用类的不必要引用。禁用 closure cleaner 后，用户的匿名 function
可能正引用一些不可序列化的调用类。这将导致序列化器出现异常。可设置的值是：
+`NONE`：完全禁用 closure cleaner ，`TOP_LEVEL`：只清理顶级类而不递归到字段中，`RECURSIVE`：递归清理所有字段。
-- `getParallelism()` / `setParallelism(int parallelism)` Set the default
parallelism for the job.
+- `getParallelism()` / `setParallelism(int parallelism)`。为作业设置默认的并行度。
-- `getMaxParallelism()` / `setMaxParallelism(int parallelism)` Set the default
maximum parallelism for the job. This setting determines the maximum degree of
parallelism and specifies the upper limit for dynamic scaling.
+- `getMaxParallelism()` / `setMaxParallelism(int
parallelism)`。为作业设置默认的最大并行度。此设置决定最大并行度并指定动态缩放的上限。
-- `getNumberOfExecutionRetries()` / `setNumberOfExecutionRetries(int
numberOfExecutionRetries)` Sets the number of times that failed tasks are
re-executed. A value of zero effectively disables fault tolerance. A value of
`-1` indicates that the system default value (as defined in the configuration)
should be used. This is deprecated, use [restart strategies]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) instead.
+- `getNumberOfExecutionRetries()` / `setNumberOfExecutionRetries(int
numberOfExecutionRetries)`。设置失败任务重新执行的次数。值为零会有效地禁用容错。`-1`
表示使用系统默认值（在配置中定义）。该配置已弃用，请改用[重启策略]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) 。
-- `getExecutionRetryDelay()` / `setExecutionRetryDelay(long
executionRetryDelay)` Sets the delay in milliseconds that the system waits
after a job has failed, before re-executing it. The delay starts after all
tasks have been successfully stopped on the TaskManagers, and once the delay is
past, the tasks are re-started. This parameter is useful to delay re-execution
in order to let certain time-out related failures surface fully (like broken
connections that have not fully timed out), before attempting a re-execution
and immediately failing again due to the same problem. This parameter only has
an effect if the number of execution re-tries is one or more. This is
deprecated, use [restart strategies]({{< ref
"docs/ops/state/task_failure_recovery" >}}#restart-strategies) instead.
+- `getExecutionRetryDelay()` / `setExecutionRetryDelay(long
executionRetryDelay)`。设置系统在作业失败后重新执行之前等待的延迟（以毫秒为单位）。在 TaskManagers
上成功停止所有任务后，开始计算延迟，一旦延迟过去，任务会被重新启动。此参数对于延迟重新执行很有用，以便在尝试重新执行并由于相同的问题立即再次失败之前，让某些超时相关的故障完全浮出水面（例如尚未完全超时的断开连接）。此参数仅在执行重试次数为一次或多次时有效。该配置已被弃用，请改用[重启策略]({{<
ref "docs/ops/state/task_failure_recovery" >}}#restart-strategies) 。
-- `getExecutionMode()` / `setExecutionMode()`. The default execution mode is
PIPELINED. Sets the execution mode to execute the program. The execution mode
defines whether data exchanges are performed in a batch or on a pipelined
manner.
+- `getExecutionMode()` / `setExecutionMode()`。默认的执行模式是
PIPELINED。设置执行模式以执行程序。执行模式定义了数据交换是以批处理方式还是以流方式执行。
-- `enableForceKryo()` / **`disableForceKryo`**. Kryo is not forced by default.
Forces the GenericTypeInformation to use the Kryo serializer for POJOs even
though we could analyze them as a POJO. In some cases this might be preferable.
For example, when Flink's internal serializers fail to handle a POJO properly.
+- `enableForceKryo()` / **`disableForceKryo`**。默认情况下不强制使用 Kryo。强制
GenericTypeInformation 对 POJO 使用 Kryo 序列化器，即使我们可以将它们作为 POJO
进行分析。在某些情况下，这可能更可取。例如，当 Flink 的内部序列化器无法正确处理 POJO 时。
-- `enableForceAvro()` / **`disableForceAvro()`**. Avro is not forced by
default. Forces the Flink AvroTypeInfo to use the Avro serializer instead of
Kryo for serializing Avro POJOs.
+- `enableForceAvro()` / **`disableForceAvro()`**。默认情况下不强制使用 Avro。强制 Flink
AvroTypeInfo 使用 Avro 序列化器而不是 Kryo 来序列化 Avro 的 POJO。
-- `enableObjectReuse()` / **`disableObjectReuse()`** By default, objects are
not reused in Flink. Enabling the object reuse mode will instruct the runtime
to reuse user objects for better performance. Keep in mind that this can lead
to bugs when the user-code function of an operation is not aware of this
behavior.
+- `enableObjectReuse()` / **`disableObjectReuse()`**。默认情况下，Flink
中不重用对象。启用对象重用模式会指示运行时重用用户对象以获得更好的性能。请记住，当一个算子的用户代码 function 没有意识到这种行为时可能会导致bug。
Review comment:
```suggestion
- `enableObjectReuse()` / **`disableObjectReuse()`**。默认情况下，Flink
中不重用对象。启用对象重用模式会指示运行时重用用户对象以获得更好的性能。请当心，当一个算子的用户代码 function 没有意识到这种行为时可能会导致bug。
```
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
