-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-53856][CORE] Remove blacklist alternative config names
#52558
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
| DeprecatedConfig("spark.rpc", "2.0", "Not used anymore."), | ||
| DeprecatedConfig("spark.scheduler.executorTaskBlacklistTime", "2.1.0", | ||
| "Please use the new excludedOnFailure options, spark.excludeOnFailure.*"), | ||
| "Not used anymore. Please use the new excludedOnFailure options, spark.excludeOnFailure.*"), |
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.
We still maintain the revised deprecation warning message to lead a new configuration name.
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.
So although users cannot use these configs after this PR, they will still be presented with the deprecation warning messages leading to new configs, right?
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.
Yes, right~
|
WDYT, @tgravescs , @cloud-fan , @HyukjinKwon , @zhengruifeng , @viirya , @mridulm , @LuciferYang , @yaooqinn , @huaxingao , @sarutak , @peter-toth ? |
peter-toth
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.
I'm ok with this change.
sarutak
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.
+1, I agree with this change too.
viirya
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 making sense.
|
Merged to master, thank you @dongjoon-hyun and all. |
beliefer
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.
Late LGTM.
|
Thank you so much, @peter-toth , @sarutak , @viirya , @HyukjinKwon , @yaooqinn , @LuciferYang , @huaxingao , @beliefer ! |
### What changes were proposed in this pull request? This PR aims to remove `blacklist` alternative config names at Apache Spark 4.1.0 while keeping the revised deprecation warning messages. ### Why are the changes needed? At Apache Spark 2.1.0, `blacklist` configurations were added. - apache#15249 At Apache Spark 3.1.0, we renamed the blacklist features roughly from `*.blacklist.*` to `*.excludeOnFailure.*`. - apache#29906 At Apache Spark 4.1.0, this PR aims to complete the removal process at Apache Spark 4.x. Note that we didn't remove these at Spark 4 in order to reduce the hurdle from 3.x to 4.x in this configuration name layer. ### Does this PR introduce _any_ user-facing change? Yes if someone still uses `*.blacklist.*` configurations. However, Apache Spark deprecated and has been warning these configurations since 3.1.0 (March 2, 2021). It's highly unlikely. ### How was this patch tested? Manual review. **BEFORE** ``` $ git grep withAlternative | grep -i blacklist | wc -l 13 ``` **AFTER** ``` $ git grep withAlternative | grep -i blacklist | wc -l 0 ``` ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#52558 from dongjoon-hyun/SPARK-53856. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Kent Yao <yao@apache.org>
What changes were proposed in this pull request?
This PR aims to remove
blacklistalternative config names at Apache Spark 4.1.0 while keeping the revised deprecation warning messages.Why are the changes needed?
At Apache Spark 2.1.0,
blacklistconfigurations were added.At Apache Spark 3.1.0, we renamed the blacklist features roughly from
*.blacklist.*to*.excludeOnFailure.*.At Apache Spark 4.1.0, this PR aims to complete the removal process at Apache Spark 4.x. Note that we didn't remove these at Spark 4 in order to reduce the hurdle from 3.x to 4.x in this configuration name layer.
Does this PR introduce any user-facing change?
Yes if someone still uses
*.blacklist.*configurations. However, Apache Spark deprecated and has been warning these configurations since 3.1.0 (March 2, 2021). It's highly unlikely.How was this patch tested?
Manual review.
BEFORE
AFTER
Was this patch authored or co-authored using generative AI tooling?
No.