-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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: DVs + Positional Deletes #11675
base: main
Are you sure you want to change the base?
Conversation
a52f450
to
221a485
Compare
283145d
to
36e65b2
Compare
782aa62
to
ffb3824
Compare
ffb3824
to
b9adfba
Compare
This pull request has been marked as stale due to 30 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the [email protected] list. Thank you for your contributions. |
core/src/main/java/org/apache/iceberg/PositionDeletesTable.java
Outdated
Show resolved
Hide resolved
Schema positionDeleteRowSchema = positionDeleteRowSchema(); | ||
StructType deleteSparkType = deleteSparkType(); | ||
StructType deleteSparkTypeWithoutRow = deleteSparkTypeWithoutRow(); | ||
if (TableUtil.formatVersion(underlyingTable(table)) >= 3) { |
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.
I think minor compaction for DVs would look quite different from the existing logic. At the very least, we don't want to keep separate jobs per partition. I'd say we should throw an exception right now if the action is called on V3 tables until we figure out a good way to perform minor compaction for DVs.
b9adfba
to
f9f58e8
Compare
f9f58e8
to
27766cb
Compare
27766cb
to
67d45e8
Compare
this is part of #11122