Skip to content
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

[SPARK-45042][BUILD] Upgrade jetty to 9.4.52.v20230823 #42761

Closed
wants to merge 2 commits into from

Conversation

panbingkun
Copy link
Contributor

What changes were proposed in this pull request?

The pr aims to Upgrade jetty from 9.4.51.v20230217 to 9.4.52.v20230823.

Why are the changes needed?

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.

@github-actions github-actions bot added the BUILD label Sep 1, 2023
@LuciferYang
Copy link
Contributor

Is the target of this pr only Spark 4.0? Or is it necessary to backport to Spark 3.5.0?
Should we migrate to using Jetty 11/12 in Spark 4.0? If yes, is this upgrade still necessary?

@panbingkun
Copy link
Contributor Author

Is the target of this pr only Spark 4.0? Or is it necessary to backport to Spark 3.5.0? Should we migrate to using Jetty 11/12 in Spark 4.0? If yes, is this upgrade still necessary?

I think we need to at least apply this PR to Spark3.5 and let me modify Jira's target.

@srowen
Copy link
Member

srowen commented Sep 2, 2023

I think this can go into 3.5 as well

@LuciferYang
Copy link
Contributor

Merged into master. There are conflicts with 3.5, could you please give a separate pr ? @panbingkun

@panbingkun
Copy link
Contributor Author

panbingkun commented Sep 4, 2023

Merged into master. There are conflicts with 3.5, could you please give a separate pr ? @panbingkun

Sure, Let me do it now.
A new separate pr for branch 3.5: #42795

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.

3 participants