[SPARK-52353][SQL] Fix bug with wrong constraints in LogicalRDDs referencing previous iterations #51056
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
…ng previous iterations
HyukjinKwon
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Remove constraints and statistics from LogicalRDDs used to store results of previous iterations.
Why are the changes needed?
In some cases logicalRDDs used for memorizing the previous iteration results produces incorrect statistics, so the filter gets pruned out, leading to an infinite recursion. We should fix this bug by removing these stats.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
The failing test case was added as a golden file. This test requires shutting off the optimization of converting small results into LocalRelation.
Was this patch authored or co-authored using generative AI tooling?
No.