Uh oh!
There was an error while loading. Please reload this page.
Allow reading dictionary encoded boolean - #3370
Merged
Merged
Conversation
I've observed some Parquet files in the wild that contain dictionary encoded boolean values, which is also wild. I don't think we want allow producing this, but I think it would be good to allow reading this. We don't judge.
wgtmac
reviewed
Dec 18, 2025
Uh oh!
There was an error while loading. Please reload this page.
wgtmac
reviewed
Dec 18, 2025
Uh oh!
There was an error while loading. Please reload this page.
wgtmac
approved these changes
Dec 19, 2025
Uh oh!
There was an error while loading. Please reload this page.
Fokko
commented
Dec 19, 2025
ContributorAuthor
Thanks @wgtmac |
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 freeto 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.
Rationale for this change
I've observed some Parquet files in the wild that contain dictionary-encoded boolean values, which is also wild.
I don't think we want to allow producing this, but I think it would be good to allow reading this. We don't judge.
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?