[SPARK-55305][SQL][TESTS] Use ParquetFooterReader.readFooter uniformly in test code to read the footer
#54086
+20
−14
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
JIRA Issue Information=== Improvement SPARK-55305 === This comment was automatically generated by GitHub Actions |
LuciferYang
changed the title
ParquetFooterReader.readFooter uniformly in test code to read the footer.ParquetFooterReader.readFooter uniformly in test code to read the footer
Contributor
Author
|
Merged into master. Thanks @dongjoon-hyun |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
This pr change to use
ParquetFooterReader.readFooteruniformly in Spark test code to read the footer.Why are the changes needed?
Use the methods encapsulated by Spark and avoid using deprecated APIs in
ParquetFileReader(specifically,ParquetFileReader#readFooter(Configuration, Path)has been deprecated).Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass Github Actions
Was this patch authored or co-authored using generative AI tooling?
No