Skip to content

Conversation

@pan3793
Copy link
Member

@pan3793 pan3793 commented Dec 9, 2025

What changes were proposed in this pull request?

This PR aims to upgrade jersey to 3.0.18 .

This is a backport of the following.

Why are the changes needed?

To bring the latest bug fixes.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Pass the CIs.

Was this patch authored or co-authored using generative AI tooling?

No.

@github-actions github-actions bot added the BUILD label Dec 9, 2025
Copy link
Contributor

@LuciferYang LuciferYang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, LGTM (pending tests)

Copy link
Member

@dongjoon-hyun dongjoon-hyun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1, LGTM.

@dongjoon-hyun
Copy link
Member

dongjoon-hyun commented Dec 9, 2025

FYI, @pan3793 ,

  • I intentionally didn't mention those info in my PR and hope to verify this commit in Apache Spark 4.1.0 release.
  • So, when you do the backport the existing commit, please respect the existing PR description like you do the cherry-pick.
    • For this PR, I revised for you by copying the existing one to here.

To @LuciferYang and @peter-toth , I intentionally didn't backport this PR to the old branches initially because I'd like to hold this until we make Apache Spark 4.1.0 successfully. We can merge this after we finish to verify via Apache Spark 4.1.0 release.

If you look at the branch-4.1, you will know that there exist several additional patches which I didn't backport in the same reasons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants