[SPARK-32037] Rename blacklisting feature to avoid language with racist connotation

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.1
• Fix Version/s: 3.1.0
• Component/s: Spark Core
• Assignee: Thomas Graves
• Reporter: Erik Krogen
• Created: 19/Jun/20 20:31
• Updated: 30/Jun/21 15:45
• Resolved: 30/Oct/20 22:19

Description

As per discussion on the Spark dev list, 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.

Issue Links

• is duplicated by: SPARK-35952 Inclusive terminology usage in Spark
• relates to: SPARK-32004 Drop references to slave
• relates to: SPARK-32036 Remove references to "blacklist"/"whitelist" language (outside of blacklisting feature)
• links to: [Github] Pull Request #29906 (tgravescs)
• links to: [Github] Pull Request #29906 (tgravescs)