[SPARK-54649][BUILD][3.5] Upgrade Jersey to 2.47 #53404
Open
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
LuciferYang
approved these changes
Dec 9, 2025
Contributor
LuciferYang
left a comment
LuciferYang
left a comment
There was a problem hiding this comment.
+1, LGTM (pending tests)
peter-toth
approved these changes
Dec 9, 2025
Member
Author
|
the pyspark-pandas-slow-connect fails consistently, likely update - root cause is no disk space, see details at #53332 (comment) |
Member
Author
|
kindly ping @zhengruifeng who author #53332 |
Contributor
|
@pan3793 https://github.com/apache/spark/actions/workflows/build_branch35_python.yml pyspark tests are green recently, the test failed in this PR also passed in the daily builds |
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?
A dependency patch version upgrade for security.
Why are the changes needed?
To fix CVE-2025-12383.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GHA.
Was this patch authored or co-authored using generative AI tooling?
No.