GH-3697: Reuse hadoop file status and footer in ParquetRecordReader - #3698
Open
steveloughran wants to merge 2 commits into
Open
GH-3697: Reuse hadoop file status and footer in ParquetRecordReader#3698steveloughran wants to merge 2 commits into
steveloughran wants to merge 2 commits into
Conversation
…ader - Ignore InputFile field in ShowFooterCommand - Create ParquetFileReader with InputFile instead of HadoopInputFile Was PARQUET-2415 Contains contributions by Claude.ai (rebasing; junit5/assertj migration) Contributed by wankunde
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
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.
Contains contributions by Claude.ai (rebasing; junit5/assertj migration)
Contributed by @wankunde; made current by claude.
Rationale for this change
HTTP HEAD is expensive, slow and comes out of your quota of a few thousand reads/second
What changes are included in this PR?
The InputFile used when reading a file footer is cached in the input split, so all splits read in the same process only will use that and any cached FileStatus when opening the file. This saves a HEAD against s3, azure and gcs on every split read within that process.
Are these changes tested?
new test, otherwise all internal.
Are there any user-facing changes?
no
Closes #3697