[AURON #2449] Add fallback coverage for unsupported Paimon scan data type - #2450
Merged
slfan1989 merged 2 commits intoAug 9, 2026
Merged
Conversation
… data types Signed-off-by: weimingdiit <weimingdiit@gmail.com>
Signed-off-by: weimingdiit <weimingdiit@gmail.com>
weimingdiit
marked this pull request as ready for review
August 6, 2026 08:03
slfan1989
approved these changes
Aug 9, 2026
slfan1989
left a comment
slfan1989
left a comment
Contributor
There was a problem hiding this comment.
Thanks for adding this regression coverage. The test verifies both the query result and that an unsupported decimal type does not enter the native Paimon scan path. LGTM.
Contributor
|
@weimingdiit Thanks for the contribution! Merged into the master. |
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
2 participants
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 #2449
Rationale for this change
Paimon native scan currently falls back when the read schema contains unsupported
data types, but this behavior was not covered by the integration tests.
Adding this regression test ensures unsupported decimal types continue to use the
Spark fallback path and do not enter native Paimon execution accidentally.
What changes are included in this PR?
Adds a Paimon integration test for an unsupported
decimal(38,10)column.The test:
NativePaimonV2TableScan.No execution logic or user-facing behavior is changed.
Are there any user-facing changes?
No user-facing changes.
How was this patch tested?
UT.