Repository navigation
GH-3877: Add VECTOR logical type support - #3876
Open
divjotarora wants to merge 2 commits into
Open
divjotarora wants to merge 2 commits into
divjotarora wants to merge 2 commits into
Conversation
Co-authored-by: Isaac <no-reply@databricks.com>
divjotarora
marked this pull request as ready for review
October 22, 2026 10:39
divjotarora
changed the title
Co-authored-by: Isaac <no-reply@databricks.com>
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
1 participant
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
The VECTOR proposal defines fixed-size vectors on canonical LIST storage, so applications can express vector semantics while retaining existing Parquet storage and interoperability. This change brings parquet-java support in line with the proposal.
What changes are included in this PR?
Adds VECTOR schema annotations and validation, checks vector values during writes, infers levels on eligible reads, and preserves LIST interoperability across existing model readers.
Are these changes tested?
The affected Maven suites for VECTOR schemas, writing, reading, adapters, and filtered reads passed, and Spotless passed for all touched modules.
Closes #3877