JunRuiLee commented on code in PR #23847:
URL: https://github.com/apache/flink/pull/23847#discussion_r1413345096
##########
docs/content.zh/docs/ops/state/task_failure_recovery.md:
##########
@@ -49,20 +49,18 @@ Flink 作业如果没有定义重启策略，则会遵循集群启动时加载
{{< generated/restart_strategy_configuration >}}
除了定义默认的重启策略以外，还可以为每个 Flink 作业单独定义重启策略。
-这个重启策略通过在程序中的 `StreamExecutionEnvironment` 对象上调用 `setRestartStrategy` 方法来设置。
-当然，对于 `StreamExecutionEnvironment` 也同样适用。
下例展示了如何给我们的作业设置固定延时重启策略。
如果发生故障，系统会重启作业 3 次，每两次连续的重启尝试之间等待 10 秒钟。
{{< tabs "2b011473-9a34-4e7b-943b-be4a9071fe3c" >}}
{{< tab "Java" >}}
Review Comment:
I appreciate your suggestion to streamline the documentation by focusing on
the options method across all languages. However, I believe it is still
essential to retain code guides for each language to ensure users have clear,
language-specific examples for configuring their Flink jobs.
Regarding the Scala API, it has indeed been deprecated as per FLIP-265 and
is scheduled to be removed in Flink 2.0. I prefer that the Scala-specific
documentation should be removed along with the actual code deprecation in the
upcoming major release.
In the case of the Python API, it was an oversight on my part not to have
deprecated it earlier. I will address this by opening a PR to deprecate the
Python API soon. Once that PR is merged, I will update the documentation
accordingly.
--
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: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
