[SPARK-52341] Upgrade Spark to 3.5.6 from 3.5.5 in Spark 3 and Iceberg integration tests #183
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
|
Maven package and Docker image is not published yet. |
…g integration tests
dongjoon-hyun
force-pushed
the
SPARK-52341
branch
from
89f21b5 to
2478513
Compare
|
Thank you, @viirya . Maven Central sync seems partial until now. I'll monitor the CIs and will merge after passing everything. |
|
All tests passed. Thank you, @viirya and @HyukjinKwon . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
This PR aims to upgrade Spark to 3.5.6 from 3.5.5 in Spark 3 and Iceberg integration tests
Why are the changes needed?
Since Apache Spark 3.5.6 is the latest release, 3.5.5 is deleted. It causes CI failures currently.
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.