[SPARK-53707] Improve attribute metadata handling. #52449
Closed
+246
−121
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?
Improve how metadata is propagated during analysis and rewrites.
This PR improves metadata propagation but it doesn't solve all the problems. A thorough review is recommended. Also recommended is to make and Alias unresolved if its inferring metadata and once its child is resolved, the ineferred metadata should be made explicit. Then the metadata would be significantly more stable.
Why are the changes needed?
Wrong metadata is inferred for DML and probably other places.
Does this PR introduce any user-facing change?
Changing metadata can change DML behavior.
Not removing aliases can cause some Project operators to remain.
How was this patch tested?
Tests were added with the previous PR on this topic [SPARK-52772].
Was this patch authored or co-authored using generative AI tooling?
No