[AURON #2321] Support Iceberg column rename and drop-then-add in the native scan#2322
Open
lyne7-sc wants to merge 4 commits into
Open
[AURON #2321] Support Iceberg column rename and drop-then-add in the native scan#2322lyne7-sc wants to merge 4 commits into
lyne7-sc wants to merge 4 commits into
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
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.
Which issue does this PR close?
Closes #2321
Rationale for this change
The native Iceberg scan matches data-file columns by name, but Iceberg tracks them by field-id. After a column rename, old files read as all-NULL; after a drop-then-add of the same name, the new column reads the old column's data.
What changes are included in this PR?
Resolve columns by Iceberg field-id instead of by name:
field_idtoField.AuronIcebergSourceUtil,IcebergScanSupport,NativeConverters): extract top-levelname → field-idfrom the scan'sexpectedSchema()and serialize it into the plan.auron-planner,scan/mod.rs): stamp the id into Arrow field metadata (PARQUET:field_id);fields_matchmatches by id when present, else falls back to case-insensitive name matching (non-Iceberg scans unchanged).Nested-struct evolution and ORC rename/drop fall back to Spark, additive evolution stays native.
Are there any user-facing changes?
Yes. Iceberg queries on renamed or drop-then-added columns now return correct results under the native scan. Unsupported cases fall back to Spark. No API change.
How was this patch tested?
Added cases to
AuronIcebergIntegrationSuite