[
https://issues.apache.org/jira/browse/FLINK-18209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17133157#comment-17133157
]
Aljoscha Krettek commented on FLINK-18209:
------------------------------------------
I don't think we should rush changing "master". There has been some
back-and-forth with this already and I think most people still confuse the
terms. The glossary defines some terms but they are a bit different from how
they are used in code and by most old-school Flink people. What used to be
called JobManager is now referred to as "Flink Master" in the glossary, the
"Flink Master" usually runs a component called JobManager but that is different
from how us OGs think of as a JobManager. And it doesn't help that the thing
the glossary calls JobManager is called JobMaster in the code, but there are
still references to JobManager in there, both for the old-style usage and the
new one.
Maybe we can just go back to calling the "Flink Master" JobManager?
> Replace "charged" words in the Flink codebase.
> ----------------------------------------------
>
> Key: FLINK-18209
> URL: https://issues.apache.org/jira/browse/FLINK-18209
> Project: Flink
> Issue Type: Task
> Reporter: Marta Paes Moreira
> Priority: Trivial
>
> The Flink codebase still makes use of "charged" words that are considered
> outdated and have a negative connotation. In particular, this is the number
> of occurrences of such words:
> "Master": 1366
> "Slave": 229
>
> "Whitelist": 23
>
> "Blacklist": 28
>
> I'd like to propose that we rethink the use of these words [1] and consider
> existing alternatives that other open source projects are also adopting.
> Replacing all occurrences is non-trivial in many cases and may involve
> breaking-changes, though, so one idea would be to break this effort down into
> different phases that can be tackled over time, depending on the impact of
> the required changes.
> [1] [https://lethargy.org/~jesus/writes/a-guide-to-nomenclature-selection/]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)