You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2019/07/09 14:43:50 UTC

[GitHub] [flink] xccui commented on a change in pull request #8995: [FLINK-13106][doc-zh]Translate Parallel Execution page into Chinese

xccui commented on a change in pull request #8995: [FLINK-13106][doc-zh]Translate Parallel Execution page into Chinese
URL: https://github.com/apache/flink/pull/8995#discussion_r301626139
 
 

 ##########
 File path: docs/dev/parallel.zh.md
 ##########
 @@ -22,29 +22,20 @@ specific language governing permissions and limitations
 under the License.
 -->
 
-This section describes how the parallel execution of programs can be configured in Flink. A Flink
-program consists of multiple tasks (transformations/operators, data sources, and sinks). A task is split into
-several parallel instances for execution and each parallel instance processes a subset of the task's
-input data. The number of parallel instances of a task is called its *parallelism*.
-
-If you want to use [savepoints]({{ site.baseurl }}/ops/state/savepoints.html) you should also consider
-setting a maximum parallelism (or `max parallelism`). When restoring from a savepoint you can
-change the parallelism of specific operators or the whole program and this setting specifies
-an upper bound on the parallelism. This is required because Flink internally partitions state
-into key-groups and we cannot have `+Inf` number of key-groups because this would be detrimental
-to performance.
+本节描述了如何在 Flink 中配置程序的并发执行。一个 Flink 程序由多个任务 task 组成(转换/算子、数据源和数据汇)。一个 task 包括多个并发执行的实例,且每一个实例都处理 task 输入数据的一个子集。一个 task 的并发实例数被称为该 task 的 *parallelism*。
 
 Review comment:
   Hi 我个人认为此处parallelism应该翻译,它和其他名词没有任何区别(我个人连task也会翻译)。关于翻译成“并行度”还是”并发度“,我个人倾向前者。除了上面提到的英文单词的区别外,”并发“有一种被迫的感觉在里面,往往代表一些比较糟糕的情况,需要小心翼翼应对;而”并行“通常标识一种主动行为,词义偏向正面。总结下来就是我个人倾向于把parallelism翻译成”并行“。

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services