[SPARK-56314][SQL][TESTS] Avoid uncessary RDD->DataFrame conversion in SQLTestData#55126
Open
zhengruifeng wants to merge 4 commits intoapache:masterfrom
Open
[SPARK-56314][SQL][TESTS] Avoid uncessary RDD->DataFrame conversion in SQLTestData#55126zhengruifeng wants to merge 4 commits intoapache:masterfrom
SQLTestData#55126zhengruifeng wants to merge 4 commits intoapache:masterfrom
Conversation
Co-authored-by: Isaac
…rsion Co-authored-by: Isaac
Co-authored-by: Isaac
Co-authored-by: Isaac
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?
Avoid uncessary RDD->DataFrame conversion in
SQLTestDataWhy are the changes needed?
1, several datasets are RDDs, but they need to be converted to DataFrame/Rows in callsites;
2, Make all datasets are DataFrames, so that they can be reused in Connect Tests in the future.
Does this PR introduce any user-facing change?
No
How was this patch tested?
CI
Was this patch authored or co-authored using generative AI tooling?
Co-authored-by: Claude Code (Opus 4.6)