Deprecate parquet::format module
#8615
Merged
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
alamb
approved these changes
Oct 14, 2025
| //! cargo run --features=cli --bin parquet-layout XYZ.parquet | ||
| //! ``` | ||
| //! | ||
| //! [`parquet-cli`]: https://github.com/apache/parquet-java/tree/master/parquet-cli |
|
Thanks @alamb! |
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.
Which issue does this PR close?
parquet::formatcrate #8572.Rationale for this change
The
parquet::formatmodule is no longer needed, but because it has been part of the public API it should go through the normal deprecation process.What changes are included in this PR?
In addition to the deprecation notice, this modifies the documentation for the
parquet-layoutbinary which relies on theformatmodule to read page headers. This tool will be removed whenformatis removed.Are these changes tested?
None needed.
Are there any user-facing changes?
Yes, public module is marked as deprecated. Not a breaking change, however.