[
https://issues.apache.org/jira/browse/SPARK-32037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159318#comment-17159318
]
Erik Krogen commented on SPARK-32037:
-------------------------------------
I think it might be helpful to frame the discussion around the components used
by this feature. It also might be worth noting that I think in the context of
this feature, the opposite term ("whitelist") is never used, so I don't think
we need to worry about the counterpart to whatever new terminology is chosen.
Here is a list of the main (non-test) blacklisting-related classes whose names
need to be changed:
* BlacklistTracker
* TaskSetBlacklist
* YarnAllocatorBlacklistTracker
Personally I still feel that a health analogy sounds most intuitive, yielding:
* HealthTracker
* TaskSetHealthReport? TaskSetUnhealthlyList?
* YarnAllocatorHealthTracker
Taking blocklist, we get:
* BlocklistTracker
* TaskSetBlocklist
* YarnAllocatorBlocklistTracker
I think it's not very intuitive... "Blocking" to me would usually imply
defending yourself against adversarial behavior (e.g. blocking a phone number,
blocking a nefarious IP address, etc.). But I am open to it -- it certainly
makes the diff easy, just one character to change :)
> 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
