Hi folks,

The parquet-java project currently declares a dependency on a pinned
version of parquet-format and dynamically pulls in the parquet.thrift file
for the pinned version.
This makes it impossible to validate and merge PRs to support new features
that have been merged into parquet-format but are not yet part of an
official parquet-format
release (https://github.com/apache/parquet-java/pull/3610 is an example).
In contrast, the arrow-rs and arrow-cpp projects have a vendored copy of
parquet.thrift in their
repos, which allows them to bypass this problem. What do folks think about
adopting this vendored approach in parquet-java?

-- Div Arora

Reply via email to