No longer allow BIT_PACKED level encoding in Parquet writer#9656
Merged
alamb merged 1 commit intoapache:mainfrom Apr 3, 2026
Merged
No longer allow BIT_PACKED level encoding in Parquet writer#9656alamb merged 1 commit intoapache:mainfrom
alamb merged 1 commit intoapache:mainfrom
Conversation
Contributor
Author
|
Note this will conflict a bit with #9653 |
Contributor
Author
|
cc @HippoBaro |
Contributor
|
Thanks, looks good to me too! |
AndreaBozzo
approved these changes
Apr 3, 2026
alamb
approved these changes
Apr 3, 2026
Contributor
|
Thanks @etseidl @HippoBaro and @AndreaBozzo |
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
5 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?
Rationale for this change
The
BIT_PACKEDencoding for repetition and definition levels has long been deprecated. Remove the possibility of using it.What changes are included in this PR?
Are these changes tested?
Should be covered by existing tests
Are there any user-facing changes?
No, only changes to API marked "experimental"