[SPARK-56031][SQL] Make Natural Join column matching respect case sensitivity conf#54858
Open
stefankandic wants to merge 2 commits intoapache:masterfrom
Open
[SPARK-56031][SQL] Make Natural Join column matching respect case sensitivity conf#54858stefankandic wants to merge 2 commits intoapache:masterfrom
stefankandic wants to merge 2 commits intoapache:masterfrom
Conversation
Contributor
Author
|
@cloud-fan please take a look when you get a change |
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
1 participant
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.
What changes were proposed in this pull request?
Use
conf.resolverinstead of case-sensitiveSeq.intersectwhen computing common column names forNATURAL JOINin the fixed-point Analyzer.Why are the changes needed?
NATURAL JOINuses case-sensitive string comparison to find common columns, ignoringspark.sql.caseSensitive(which defaults tofalse). This causesNATURAL JOINto silently degrade to aCROSS JOINwhen columns differ only in case (e.g.,IDvsid).The equivalent
USINGjoin already handles this correctly.Does this PR introduce any user-facing change?
No.
How was this patch tested?
New unit and e2e tests in golden files.
Was this patch authored or co-authored using generative AI tooling?
No.