[
https://issues.apache.org/jira/browse/SPARK-32036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Graves resolved SPARK-32036.
-----------------------------------
Fix Version/s: 3.1.0
Resolution: Fixed
> Remove references to "blacklist"/"whitelist" language (outside of
> blacklisting feature)
> ---------------------------------------------------------------------------------------
>
> Key: SPARK-32036
> URL: https://issues.apache.org/jira/browse/SPARK-32036
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 3.0.1
> Reporter: Erik Krogen
> Priority: Minor
> Fix For: 3.1.0
>
>
> As per [discussion on the Spark dev
> list|https://lists.apache.org/thread.html/rf6b2cdcba4d3875350517a2339619e5d54e12e66626a88553f9fe275%40%3Cdev.spark.apache.org%3E],
> it will be beneficial to remove references to problematic language that can
> alienate potential community members. One such reference is "blacklist" and
> "whitelist". While it seems to me that there is some valid debate as to
> whether these terms have racist origins, the cultural connotations are
> inescapable in today's world.
> Renaming the entire blacklisting feature would be a large effort with lots of
> care needed to maintain public-facing APIs and configurations. Though I think
> this will be a very rewarding effort for which I've filed SPARK-32037, I'd
> like to start by tackling all of the other references to such terminology in
> the codebase, of which there are still dozens or hundreds beyond the
> blacklisting feature.
> I'm not sure what the best "Component" is for this so I put Spark Core for
> now.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
