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.
[AURON #2434] Support full-data-file Iceberg changelog deletes #2435
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
base: master
Are you sure you want to change the base?
[AURON #2434] Support full-data-file Iceberg changelog deletes #2435
Changes from all commits
5f8f024c0fea01f3db3dfFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
This replaces the previous
falls back when delete changes existtest, which covered row-level deletes. Could we keep a dedicated fallback test (e.g. non-partitioned table with a position delete, or a DeletedDataFileScanTask with non-empty existingDeletes())? It would help guard against regressions on the row-level delete / update paths.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.
Thanks for pointing this out. I rechecked the behavior of the replaced test and Iceberg 1.10.1.
The replaced test did not actually exercise a row-level delete. In the CI run, the insert produced two data files and the DELETE removed one complete data file, so it covered a DeletedDataFileScanTask with empty existingDeletes(), which is the case this PR now makes native.
A genuine position-delete changelog case cannot currently reach Auron's fallback guard. BaseIncrementalChangelogScan rejects any snapshot in the changelog range that contains delete manifests before Auron receives the planned tasks. In addition, Iceberg 1.10.1's CreateDataFileChangeTasks constructs both AddedRowsScanTask and DeletedDataFileScanTask with NO_DELETES, so a DeletedDataFileScanTask with non-empty existingDeletes() cannot be produced through the public changelog planner.
The existing "iceberg scan falls back when delete files exist" test still covers position-delete fallback for regular Iceberg scans. It explicitly creates a position delete, verifies that the planned FileScanTask contains deletes, and checks that NativeIcebergTableScan is not used.
Given these limitations, I have not added a changelog integration test that would either fail inside Iceberg before reaching Auron or not exercise the intended guard. If useful, I can add a focused synthetic task-level test for the existingDeletes() guard instead.
Uh oh!
There was an error while loading. Please reload this page.