[SPARK-46723][CONNECT][SCALA] Make addArtifact retryable #44740
Closed
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
Contributor
Author
hvanhovell
reviewed
Jan 15, 2024
| .connectionString(s"sc://localhost:${server.getPort}") | ||
| .interceptor(new ClientInterceptor { | ||
| override def interceptCall[ReqT, RespT]( | ||
| methodDescriptor: MethodDescriptor[ReqT, RespT], |
Contributor
Author
|
Tests green! |
HyukjinKwon
approved these changes
Jan 16, 2024
Member
|
Merged to master. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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?
Make addArtifact API retrying on errors.
Note this is safe operation since addArtifact is idempotent operation (#43314)
Why are the changes needed?
For the same reasons as we make other API retryable.
Does this PR introduce any user-facing change?
Yes
How was this patch tested?
Added test.
Testing by hand against custom spark server.
Was this patch authored or co-authored using generative AI tooling?
No & never