Repository navigation
GH-51143: [Format] Add Parquet FILE canonical extension type - #51248
Open
Mandukhai-Alimaa wants to merge 2 commits into
Open
Mandukhai-Alimaa wants to merge 2 commits into
Mandukhai-Alimaa wants to merge 2 commits into
Conversation
|
|
Author
|
CC: @rok |
Mandukhai-Alimaa
force-pushed
the
mandy/file/format
branch
from
September 16, 2026 17:33
8010628 to
60aecdb
Compare
wgtmac
reviewed
Oct 21, 2026
|
|
||
| Extension metadata is an empty string. | ||
|
|
||
| Field semantics |
Member
There was a problem hiding this comment.
For this section, should we quote the Parquet spec verbatim with explicit attribution at the start, or keep the current wording and label it as “adapted from the Parquet FILE logical type specification”? Either way, it would help to make the relationship explicit so readers know whether this is a direct quotation or a restatement intended to preserve the same semantics.
Contributor
There was a problem hiding this comment.
unless there is a good reason to restate all the content, I think it should simply point at the Parquet spec
alamb
reviewed
Oct 22, 2026
alamb
left a comment
alamb
left a comment
Contributor
There was a problem hiding this comment.
Thank you for working on this @Mandukhai-Alimaa
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
3 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
As storage formats standardize file-level references, Arrow needs a canonical in-memory representation to preserve these semantics across IPC streams, the C Data Interface, Arrow Flight, and language bindings. Without a canonical extension type, file fields lose their semantic metadata during serialization.
[DISCUSS] thread in the mailing list
What changes are included in this PR?
Proposal and documentation for the
arrow.parquet.filecanonical extension type.Are these changes tested?
N/A
Are there any user-facing changes?
Yes, this is an extension to the arrow format.