You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2020/06/11 12:48:00 UTC
[jira] [Comment Edited] (FLINK-18209) Replace "charged" words in
the Flink codebase.
[ https://issues.apache.org/jira/browse/FLINK-18209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17133202#comment-17133202 ]
Stephan Ewen edited comment on FLINK-18209 at 6/11/20, 12:47 PM:
-----------------------------------------------------------------
+1 from my side
The most visible part is probably the "slave" file, which we may be able to change in 1.11 even.
AS far as I can tell, it is only used by the "start/stop-cluster.sh" scripts, so might me simple to change.
We need a prominent release note, though, that this breaks existing standalone setups. On the other hand, I think few production installations are actually based on these scripts.
was (Author: stephanewen):
Let's do it.
The most visible part is probably the "slave" file, which we may be able to change in 1.11 even.
AS far as I can tell, it is only used by the "start/stop-cluster.sh" scripts, so might me simple to change.
We need a prominent release note, though, that this breaks existing standalone setups. On the other hand, I think few production installations are actually based on these scripts.
> 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)