apache
[SPARK-54648][BUILD][4.0] Upgrade Jersey to 3.0.18
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.
- https://github.com/apache/spark/pull/51949
Why are the changes needed?
To bring the latest bug fixes.
- https://github.com/eclipse-ee4j/jersey/compare/3.0.17...3.0.18
- https://github.com/eclipse-ee4j/jersey/pull/5891 (Support Java 25)
- https://github.com/eclipse-ee4j/jersey/pull/5822
- https://projects.eclipse.org/projects/ee4j.jersey/releases/3.0.18
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.
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.
- #51949
- 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.
@dongjoon-hyun, this is actually a combination of SPARK-53223 and SPARK-51543 from the backport perspective, should I add both of their original descriptions?
@dongjoon-hyun, this is actually a combination of SPARK-53223 and SPARK-51543 from the backport perspective, should I add both of their original descriptions?
Hi, @pan3793 . Thank you for double-checking.
However, we don't consider in that accumulated way. This is a simple and obvious backport of Jersey 3.0.18 dependency change (one-liner) with regenerated result of dev/deps/spark-deps-hadoop-3-hive-2.3 on branch-4.0.
If there is any other code change, it might be consider as you mentioned. There is no other code contribution from SPARK-51543, isn't it?
SPARK-51543: (master) upgrade Jersey from 3.0.16 => 3.0.17 SPARK-52223: (master) upgrade Jersey from 3.0.17 => 3.0.18 this one: (branch-4.0) upgrade Jersey 3.0.16 => 3.0.18
then the current state is good enough, it's ready to go.
However, we don't consider in that accumulated way.
