[SPARK-53734][SQL] Prefer table column over LCA when resolving array index #52472
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?
Prefer table column over LCA when resolving array index.
Why are the changes needed?
For a query like:
the output should be (1,1), but current Spark implementation outputs (1,2). This is because
[col1]
is resolved as an LCA instead of being resolved to a column. This is because we never actually resolvefield
ofUnresolvedExtractValue
ininnerResolve
, so the resolution offield
fails over to the next item in precedence chain, which is LCA.Does this PR introduce any user-facing change?
Yes, user now sees the correct result for the impacted query shape
How was this patch tested?
Added test case for the impacted query.
Was this patch authored or co-authored using generative AI tooling?
No