-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-48230][BUILD] Remove unused jodd-core
#46520
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
dongjoon-hyun
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, LGTM (Pending CIs)
jodd-core
|
Merged to master for Apache Spark 4.0.0. |
|
Hi, @pan3793 . It seems that we need to re-evaluate this dependency removal. Please see the following which is related to |
|
For the existing Hive UDFs which assumes Sorry but let me revert this first. We need a more graceful way of removing or additional verified migration path (documentation and config). |
|
@dongjoon-hyun Okay, as this fail the CI, we should revert deps removing first and do more investigation later. While for supporting "legacy Hive UDF jars", I think if the user imports some classes that come from Hive transitive deps, Spark is not responsible for handling that. Spark only includes part of Hive deps (I mean all jars shipped by Hive binary tgz), for example, Hive ships I believe jodd/commons-lang 2.x/jackson 1.x are in same position. |
|
Hi, @dongjoon-hyun, since we have successfully upgraded Hive to 2.3.10 in Spark 4.0, do you think we can re-evaluate this PR for Spark 4.1? |
+1, @pan3793 . |
|
cc @peter-toth |
What changes were proposed in this pull request?
Remove a jar that has CVE GHSA-jrg3-qq99-35g7
Why are the changes needed?
Previously,
jodd-corecame from Hive transitive deps, while apache/hive#5151 (Hive 2.3.10) cut it out, so we can remove it from Spark now.Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GA.
Was this patch authored or co-authored using generative AI tooling?
No.