[AURON #2427] Report fallback reason for unsupported Iceberg scan data types#2428
Open
weimingdiit wants to merge 1 commit into
Open
[AURON #2427] Report fallback reason for unsupported Iceberg scan data types#2428weimingdiit wants to merge 1 commit into
weimingdiit wants to merge 1 commit into
Conversation
…an data types Signed-off-by: weimingdiit <weimingdiit@gmail.com>
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 #2427
Rationale for this change
Auron Iceberg native scan can fall back when the Iceberg scan schema contains data types that are not supported by native scan conversion.
Before this change, unsupported metadata columns already had a clear fallback reason, but unsupported data columns did not. This made it harder to diagnose why an Iceberg scan stayed on Spark execution.
What changes are included in this PR?
Adds an Iceberg fallback reason for unsupported scan schema data types.
Reports unsupported field names and Spark SQL types in the never-convert reason.
Extends the existing unsupported decimal Iceberg scan test to check the fallback reason.
Are there any user-facing changes?
No API changes. Users may see a clearer fallback reason when an Iceberg native scan is skipped because of unsupported data types.
How was this patch tested?
UT.
Was this patch authored or co-authored using generative AI tooling?