feat: define nested field path contract#351
Merged
Merged
Conversation
github-actions
Bot
added
python
Contributor
|
ACTION NEEDED The PR title and description are used as the merge commit message. Please update your PR title and description to match the specification. For details on the error please inspect the "PR Title Check" action. |
Xuanwo
changed the title
BubbleCal
approved these changes
Jun 10, 2026
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.
This PR defines the Lance Namespace contract for nested field paths across OpenAPI schemas and generated client/server documentation.
The previous contract described many inputs as column names, which left nested fields, literal dots, escaped segments, ambiguous leaf names, and canonical display/error behavior underspecified. The new
FieldPathschema aligns these APIs with Lance field path syntax while preserving existing wire field names for compatibility.Generated Python, Java, Rust clients and docs are refreshed from the updated OpenAPI spec, and a repository-level contract test guards the key schema references.