Handle runtime Parquet Hadoop API version via reflection#330
Merged
Conversation
55dd08a to
5629587
Compare
This was referenced Dec 10, 2025
EnricoMi
added a commit
that referenced
this pull request
Dec 10, 2025
EnricoMi
added a commit
that referenced
this pull request
Dec 10, 2025
d660b45 to
36083e1
Compare
36083e1 to
d18c7af
Compare
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
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.
Runtime and compile time version of Parquet Hadoop and its dependencies can vary. The runtime version is either given by Spark or by the user. This replaces Spark version specific code with single implementation for all Spark and Parquet Hadoop versions. Compile time uses the latest Parquet Hadoop version, runtime checks existence of methods in actual version via reflection.