[
https://issues.apache.org/jira/browse/SPARK-32333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17405814#comment-17405814
]
Thomas Graves commented on SPARK-32333:
---------------------------------------
I was looking to break this up into subtasks but not sure how much we will be
able to, perhaps something like this:
Note we need to keep backwards compatibility so rename is copy for any public
api's/scripts.
Also note, one thing we may not want to change or discuss more is rename
ApplicationMaster since that is the name Hadoop uses for it. We can certainly
change internal api's and functions but external we may not want to.
1) Rename the standalone Master and public apis (SparkConf.setMaster), scripts,
docs that reference those scripts
2) Rename standalone Master classes that aren't public - MasterArguments,
MasterUI, MasterMessages, etc
3) Rename internal classes and messages with Master in name, note we could also
rename class with Master in the name of them like BlockManagerMaster,
MapOutputTrackerMaster, etc. We could break this up further if people are
interesting in helping.
> Drop references to Master
> -------------------------
>
> Key: SPARK-32333
> URL: https://issues.apache.org/jira/browse/SPARK-32333
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core, SQL
> Affects Versions: 3.0.0
> Reporter: Thomas Graves
> Priority: Major
>
> We have a lot of references to "master" in the code base. It will be
> beneficial to remove references to problematic language that can alienate
> potential community members.
> SPARK-32004 removed references to slave
>
> Here is a IETF draft to fix up some of the most egregious examples
> (master/slave, whitelist/backlist) with proposed alternatives.
> https://tools.ietf.org/id/draft-knodel-terminology-00.html#rfc.section.1.1.1
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
