fix(parquet): restore Arrow duration units from schema metadata - #1095
Merged
zeroshade merged 1 commit intoAug 6, 2026
Merged
Conversation
zeroshade
approved these changes
Aug 5, 2026
fallintoplace
changed the title
fallintoplace
changed the title
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
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
Parquet stores durations as unannotated INT64 because it has no duration logical type. When stored Arrow schema metadata says the original field was a duration, the reader currently keeps the inferred int64 type and loses the unit.
What changes are included in this PR?
Restore the original duration type when the stored origin type is a duration and Parquet inference produced int64. Keep the change limited to this schema restoration case.
Are these changes tested?
go test ./parquet/pqarrow -run TestRestoreDurationFromStoredSchema -count=1Are there any user-facing changes?
No API changes. This corrects the reported behavior while preserving the existing ownership and compatibility contracts.