Introduce FileType reference implementation - #10109
Open
brkyvz wants to merge 4 commits into
Open
Conversation
etseidl
reviewed
Jun 10, 2026
etseidl
left a comment
etseidl
left a comment
Contributor
There was a problem hiding this comment.
Looks good, just one test nit.
I marked this as a breaking change since it adds a variant to a public enum.
| assert!(result | ||
| .unwrap_err() | ||
| .to_string() | ||
| .contains("unrecognized field")); |
Contributor
There was a problem hiding this comment.
Nit: in general I prefer full string compares to contains. In this case it should at least test for the specific unrecognized field name 'unknown_field'.
Contributor
|
Looking very nice. Could you also add a roundtrip test to/from parquet? 🙏 Also, do you have any plans to add a |
etseidl
added
the
next-major-release
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.
Which issue does this PR close?
TODO
Rationale for this change
Introduces the reference implementation for the new LogicalTypeAnnotation File as discussed in this design document
What changes are included in this PR?
Introduces a new LogicalTypeAnnotation called FILE. It enforces that a group with this type annotation have the following fields by name:
Are these changes tested?
Yes, unit tested
Are there any user-facing changes?
Introduces a new LogicalTypeAnnotation called FILE