[AURON #1610] Handle case-insensitive columns in NativeHiveTableScanBase #1611
+1
−1
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
merrily01
changed the title
Contributor
|
@Flyangz Thank you for your contribution. But can you add a test to verify the fix for this issue? |
richox
previously approved these changes
Nov 11, 2025
Contributor
|
can this change handle columns that appear only in filter predicates but not in output? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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 #1610
Rationale for this change
Make
NativeFileSourceScanBase.nativeFileSchemacan handle uppercase column name.What changes are included in this PR?
Use
outputinstead ofrequestedAttributesto match.Are there any user-facing changes?
no
How was this patch tested?
manually