[SPARK-33741][FOLLOW-UP][CORE] Rename the min threshold time speculation config#33037
Closed
Ngone51 wants to merge 1 commit intoapache:masterfrom
Closed
[SPARK-33741][FOLLOW-UP][CORE] Rename the min threshold time speculation config#33037Ngone51 wants to merge 1 commit intoapache:masterfrom
Ngone51 wants to merge 1 commit intoapache:masterfrom
Conversation
Member
Author
cloud-fan
approved these changes
Jun 23, 2021
|
Kubernetes integration test starting |
|
Kubernetes integration test status failure |
|
Test build #140188 has finished for PR 33037 at commit
|
HyukjinKwon
approved these changes
Jun 23, 2021
Contributor
|
thanks, merging to master! |
Member
Author
|
thanks all!! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This's a follow-up of #30710.
Rename the conf from
spark.speculation.min.thresholdtospark.speculation.minTaskRuntime.Why are the changes needed?
To follow the config naming policy.
Does this PR introduce any user-facing change?
No (since Spark 3.2 hasn't been released).
How was this patch tested?
Pass existing tests.