[
https://issues.apache.org/jira/browse/FLINK-23225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jark Wu closed FLINK-23225.
---------------------------
Fix Version/s: 1.14.0
Assignee: wuguihu
Resolution: Fixed
Fixed in master: bf7bd78f8a6065b8de1d94fdb97fc094cdf0ac3d
> There is some mismatches between the current translation and the latest
> English version on the Flink-Architecture page
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-23225
> URL: https://issues.apache.org/jira/browse/FLINK-23225
> Project: Flink
> Issue Type: Bug
> Components: Documentation
> Reporter: wuguihu
> Assignee: wuguihu
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.14.0
>
> Attachments: image-20210703235017401.png
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> There is some mismatches between the current translation and the latest
> English version on the Flink-Architecture page
>
>
> The original English text is as
> follows([https://ci.apache.org/projects/flink/flink-docs-master/docs/concepts/flink-architecture/#flink-application-execution])：
>
> {code:java}
> A Flink Application is any user program that spawns one or multiple Flink
> jobs from its ``main()`` method. The execution of these jobs can happen in a
> local JVM (``LocalEnvironment``) or on a remote setup of clusters with
> multiple
> machines (``RemoteEnvironment``). For each program, the
> `ExecutionEnvironment`
> provides methods to control the job execution (e.g. setting the parallelism)
> and to interact with
> the outside world (see [Anatomy of a Flink Program](< ref
> "docs/dev/datastream/overview" >#anatomy-of-a-flink-program)).
>
> The jobs of a Flink Application can either be submitted to a long-running
> [Flink Session Cluster](< ref "docs/concepts/glossary"
> >#flink-session-cluster), a dedicated [Flink Job
> Cluster](< ref "docs/concepts/glossary" >#flink-job-cluster), or a
> [Flink Application Cluster](< ref "docs/concepts/glossary"
> >#flink-application-cluster). The difference between these options is mainly
> related to the cluster’s lifecycle and to resource
> isolation guarantees.
>
> {code}
>
>
> *The Chinese translation is as follows*
> {code:java}
> Flink 应用程序 是从其 ``main()`` 方法产生的一个或多个 Flink 作业的任何用户程序。这些作业的执行可以在本地
> JVM（`LocalEnvironment``）中进行，或具有多台机器的集群的远程设置（``RemoteEnvironment``）中进行。对于每个程序，[``ExecutionEnvironment``]({{
> site.javadocs_baseurl }}/api/java/) 提供了一些方法来控制作业执行（例如设置并行度）并与外界交互（请参考 [Flink
> 程序剖析](< ref "docs/dev/datastream/overview" >#anatomy-of-a-flink-program) ）。
>
> Flink 应用程序的作业可以被提交到长期运行的 [Flink Session 集群](< ref "docs/concepts/glossary"
> >#flink-session-cluster)、专用的 [Flink Job 集群](< ref "docs/concepts/glossary"
> >#flink-job-cluster) 或 [Flink Application 集群](< ref "docs/concepts/glossary"
> >#flink-application-cluster)。这些选项之间的差异主要与集群的生命周期和资源隔离保证有关。
> {code}
>
> The incorrect translation is as follows:
> {code:java}
> //1
> JVM（`LocalEnvironment``） should be JVM（`LocalEnvironment`）
>
> //2
> [``ExecutionEnvironment``]({{ site.javadocs_baseurl }}/api/java/) should be
> `ExecutionEnvironment`
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
