[SPARK-43033][SQL] Avoid task retries due to AssertNotNull checks#40703
Closed
xiaochen-zhou wants to merge 5 commits into
Closed
[SPARK-43033][SQL] Avoid task retries due to AssertNotNull checks#40703xiaochen-zhou wants to merge 5 commits into
xiaochen-zhou wants to merge 5 commits into
Conversation
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
1 participant
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 PR update the task retry logic to not retry if the exception has an error class which means a user error.
Why are the changes needed?
As discussed here, tasks that failed because of exceptions generated by AssertNotNull should not be retried.
Does this PR introduce any user-facing change?
No
How was this patch tested?
This PR comes with tests.