[SPARK-46732][CONNECT][3.5]Make Subquery/Broadcast thread work with Connect's artifact management #44763
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?
Similar with SPARK-44794, propagate JobArtifactState to broadcast/subquery thread.
This is an example:
Before this pr, this example will throw exception
ClassNotFoundException
. Subquery and Broadcast execution use a separate ThreadPool which don't have theJobArtifactState
.Why are the changes needed?
Fix bug. Make Subquery/Broadcast thread work with Connect's artifact management.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Add a new test to
ReplE2ESuite
Was this patch authored or co-authored using generative AI tooling?
No