Support previously and currently documented encodings for boolean lists in rust compact protocol #3094
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.
In apache/datafusion#14281 it was noticed that the go parquet implementation writes metadata containing boolean lists in an unexpected encoding. The collection type was encoded as
0x02, which the documentation now specifies as an allowed alternative value to0x01. The values were encoded as 0 (false) and 1 (true), which matches a previous version of the documentation (see documentation update in 2c29c56). This change makes the rustTCompactInputProtocolsupport both variations.Happy to create a jira ticket if needed.
[skip ci]anywhere in the commit message to free up build resources.