[
https://issues.apache.org/jira/browse/SPARK-32037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184144#comment-17184144
]
Micah Kornfield commented on SPARK-32037:
-----------------------------------------
FWIW one argument for using 'denylist' is it is the shortest option (which
only matters when all other things are equal).
An argument against 'blocklist' is it is easy to have regressions via typo.
> Rename blacklisting feature to avoid language with racist connotation
> ---------------------------------------------------------------------
>
> Key: SPARK-32037
> URL: https://issues.apache.org/jira/browse/SPARK-32037
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 3.0.1
> Reporter: Erik Krogen
> Priority: Minor
>
> 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".
> While it seems to me that there is some valid debate as to whether this term
> has racist origins, the cultural connotations are inescapable in today's
> world.
> I've created a separate task, SPARK-32036, to remove references outside of
> this feature. Given the large surface area of this feature and the
> public-facing UI / configs / etc., more care will need to be taken here.
> I'd like to start by opening up debate on what the best replacement name
> would be. Reject-/deny-/ignore-/block-list are common replacements for
> "blacklist", but I'm not sure that any of them work well for this situation.
--
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
