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: Backport Spark 3.5 DVs related part to Spark 3.4 #12603

Merged
merged 2 commits into from
Mar 21, 2025

Conversation

tomtongue
Copy link
Contributor

@tomtongue tomtongue commented Mar 21, 2025

This PR backports the Spark 3.5 Deletion Vectors related part including tests into Spark 3.4, to reflect the changes in #12048 and #11485 to Spark 3.4 as well . The following classes in the actions package are mainly included:

@github-actions github-actions bot added the spark label Mar 21, 2025
@tomtongue tomtongue changed the title Spark: Backport Spark 3.5 DV related part to Spark 3.4 Spark: Backport Spark 3.5 DVs related part to Spark 3.4 Mar 21, 2025
@tomtongue
Copy link
Contributor Author

tomtongue commented Mar 21, 2025

@nastra Add some DVs related tests including V3 fields addition to SparkContent. Could you check the changes? If there's any additional files that I should add or some changes that should be removed, please let me know.

Copy link
Contributor

@nastra nastra left a comment

Choose a reason for hiding this comment

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

thanks @tomtongue for handling this

@nastra nastra merged commit 74051b4 into apache:main Mar 21, 2025
27 checks passed
@tomtongue
Copy link
Contributor Author

@nastra Thank you! (and I should've shared this earlier for the PR, thanks!)

@tomtongue tomtongue deleted the spark3.4-dv-test-backport branch March 21, 2025 17:16
lliangyu-lin pushed a commit to lliangyu-lin/iceberg that referenced this pull request Mar 23, 2025
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.

2 participants