-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-32036] Replace references to blacklist/whitelist language with more appropriate terminology, excluding the blacklisting feature. #28874
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@holdenk can you help review? |
|
Sure, I'm taking this weekend away from coding so I'll get to this early next week. |
|
Updated to address @venkata91 's comments and fix one class I missed in the |
|
ok to test |
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala
Outdated
Show resolved
Hide resolved
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/json/JSONOptions.scala
Outdated
Show resolved
Hide resolved
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/json/JsonSuite.scala
Show resolved
Hide resolved
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveQueryFileTest.scala
Show resolved
Hide resolved
|
Test build #124427 has finished for PR 28874 at commit
|
5963b54 to
32ccda7
Compare
|
Updated to resolve whitespace errors and some typos per suggestions by @tgravescs . Thanks! |
|
Test build #124492 has finished for PR 28874 at commit
|
|
I'm not sure why the Jenkins build failed. I see this message: I do not understand how it could be related to my patch, which doesn't touch anything Maven-related. Any suggestions? |
|
Yeah I've been running into that too. I reached out to Shane and he took the worker that has the corrupted m2 cache out of rotation. So if we do "Jenkins retest this please" hopefully the other Jenkin's workers have a better m2 cache :) |
holdenk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this, I'm happy that we are cleaning this up :)
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala
Outdated
Show resolved
Hide resolved
sql/hive/src/test/scala/org/apache/spark/sql/hive/execution/HiveQueryFileTest.scala
Show resolved
Hide resolved
|
Test build #124497 has finished for PR 28874 at commit
|
|
Test build #124500 has finished for PR 28874 at commit
|
core/src/main/scala/org/apache/spark/deploy/history/FsHistoryProvider.scala
Show resolved
Hide resolved
|
Test build #124552 has finished for PR 28874 at commit
|
tgravescs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me. @holdenk any other comments?
srowen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like it's all internal changes, with no behavior changes, so seems fine to me.
core/src/main/scala/org/apache/spark/deploy/rest/RestSubmissionClient.scala
Show resolved
Hide resolved
srowen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks OK to me, any more comments? I can merge if not.
Let me run tests one more time to be sure.
|
Jenkins test this please |
|
Test build #125689 has finished for PR 28874 at commit
|
|
LGTM but we have a merge conflict now |
|
@xkrogen can you up merge? |
09ec2e8 to
5cd7d81
Compare
|
Thanks a lot for the new eyes @srowen and @tgravescs ! I've just pushed up a resolution to the conflict. |
|
Test build #125780 has finished for PR 28874 at commit
|
|
@xkrogen unfortunately it appears there is another conflict could you update again? |
… more appropriate terminology, excluding the blacklisting feature.
…nt, rename one variable based on feedback.
…the initial commit.
…rceDownloadSchemas to forceDownloadSchemes
5cd7d81 to
1ba58fb
Compare
|
Playing a game of whack-a-mole here :) Thanks for the heads up @tgravescs . Pushed up another conflict resolution. |
|
Test build #125843 has finished for PR 28874 at commit
|
|
I think the pip packaging test failure is not related to my changes, but I cannot really tell. |
|
all GitHub action tests passed so I think we are good. I'll kick it once more just to check. |
|
test this please |
|
Test build #125852 has finished for PR 28874 at commit
|
|
@xkrogen unfortunately think we are still playing wack a mole, it doesn't seem mergable, could you upmerge again and I'll try to watch closely and get merged. |
|
@tgravescs GitHub seems to be reporting no conflicts, and when I just put together a rebase, there were also no conflicts. Can you check again? I'm happy to push up a rebased branch, but don't want to have to wait for another test cycle if it's not necessary :) |
|
weird, let me try to commit again, it was reporting couldn't do it, but I also saw this PR was stuck and wouldn't say if it was mergeable |
|
thanks @xkrogen merged to master |
|
Thanks a lot @tgravescs ! |
| PY2_CLASS_DICT_BLACKLIST = (PY2_METHOD_WRAPPER_TYPE, | ||
| PY2_WRAPPER_DESCRIPTOR_TYPE) | ||
| PY2_CLASS_DICT_SKIP_PICKLE_METHOD_TYPE = (PY2_METHOD_WRAPPER_TYPE, | ||
| PY2_WRAPPER_DESCRIPTOR_TYPE) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey let's dont change this file but keep as the release (and fix their release and port it together). It's the exact copy of cloudpickle release. We just port their fixes and dont have conflicts here for management purpose. Linters skip this file too and we had to put a lot of efforts to resolve the conflicts here before.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am going to upgrade this file at #29114. Seems that release version doesn't have this issue.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok so since you are upgrading, we are good to leave it as is, correct? Your merge will fix it up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, I think we're all good
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for addressing this @HyukjinKwon ! I avoided making changes in other files that I could tell were direct copies (e.g. stuff in hive-thriftserver) but did not realize this was one of those cases.
|
+1 the changes look good |
What changes were proposed in this pull request?
This PR will remove references to these "blacklist" and "whitelist" terms besides the blacklisting feature as a whole, which can be handled in a separate JIRA/PR.
This touches quite a few files, but the changes are straightforward (variable/method/etc. name changes) and most quite self-contained.
Why are the changes needed?
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" 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.
Does this PR introduce any user-facing change?
In the test file
HiveQueryFileTest, a developer has the ability to specify the system propertyspark.hive.whitelistto specify a list of Hive query files that should be tested. This system property has been renamed tospark.hive.includelist. The old property has been kept for compatibility, but will log a warning if used. I am open to feedback from others on whether keeping a deprecated property here is unnecessary given that this is just for developers running tests.How was this patch tested?
Existing tests should be suitable since no behavior changes are expected as a result of this PR.