fix: optional schema fields are always set to 0 #24
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.
SchemaElement
int32 optional fields likeFieldId
,Scale
,Precision
etc. are always serialised with value 0.See for example the schema generated for the example in
_examples/people/
:returns
This can have unintended consequences with any Parquet reader that explicitly uses the schema.
Additionally the fields are only serialised if they are not
nil
, see here.With the proposed changes the schema for the example in
_examples/people/
is: