[SPARK-45837][CONNECT] Improve logging information in handling retries#43719
Closed
cdkrot wants to merge 2 commits intoapache:masterfrom
Closed
[SPARK-45837][CONNECT] Improve logging information in handling retries#43719cdkrot wants to merge 2 commits intoapache:masterfrom
cdkrot wants to merge 2 commits intoapache:masterfrom
Conversation
Contributor
Author
dongjoon-hyun
changed the title
Member
|
Could you re-trigger CI, @cdkrot ? |
Contributor
Author
|
Had retriggered |
HyukjinKwon
approved these changes
Nov 10, 2023
Member
|
Merged to master. |
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?
Add suppressed exception when handling retries
Why are the changes needed?
Improves user and debugging experience by showing underlying error.
Does this PR introduce any user-facing change?
Better exceptions.
How was this patch tested?
Hand testing
Was this patch authored or co-authored using generative AI tooling?
NA