knaufk commented on a change in pull request #8607: [FLINK-12652] [documentation] add first version of a glossary URL: https://github.com/apache/flink/pull/8607#discussion_r300397299
########## File path: docs/concepts/glossary.md ########## @@ -0,0 +1,167 @@ +--- +title: Glossary +nav-pos: 3 +nav-title: Glossary +nav-parent_id: concepts +--- +<!-- +Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. +--> + +#### Flink Application Cluster + +A Flink Application Cluster is a dedicated [Flink Cluster](#flink-cluster) that only +executes a single [Flink Job](#flink-job). The lifetime of the +[Flink Cluster](#flink-cluster) is bound to the lifetime of the Flink Job. Formerly +Flink Application Clusters were also known as Flink Clusters in *job mode*. Compare to +[Flink Session Cluster](#flink-session-cluster). + +#### Flink Cluster + +A distributed system consisting of (typically) one +[Flink JobManager Process](#flink-jobmanager-process) and one or more Review comment: I think, we have three options: 1. Rename "JobManager Process" to "Flink Master" now in the glossary. This would be in line with the future vision, but will create a lot of inconsistencies (e.g. naming of scripts and commands in the binary distribution), which we can not fix as part of the glossary. Redirect can mitigate this a bit. 2. Stick with "JobManager Process" right now and rename later consistently. 3. Stick with "JobManager" forever and rename the component to "JobMaster" in accordance to the code. I think, it is too late for this (all FLIP-6 documents talk about "JobManager") and the names would also not be very descriptive and very similar. I am happy with 1. and 2., but not so much with option 3. @tillrohrmann, @StephanEwen: What do you think? ---------------------------------------------------------------- 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] With regards, Apache Git Services
