Repository navigation
feat(blob): expose managed sharing in Python preparation API - #9880
Merged
Merged
Conversation
There was a problem hiding this comment.
Claude Code Review
This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.
Tip: disable this comment in your organization's Code Review settings.
BubbleCal
approved these changes
Oct 11, 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
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.
Prepared Blob writes can fail when Python's logical field carries empty Arrow extension metadata and a prepared field omits it. Accept those equivalent representations specifically for
lance.blob.v2, including nested fields, while retaining strict checks for other extensions and nonempty metadata.Expose
BlobDescriptorArrayBuilder.append_managedin Python so callers can reuse an existing immutable payload or byte range within a table without assembling raw descriptor structs. Validation stays in the Rust core. The guide documents snapshot protection, base identity, and Managed-aware maintenance requirements.Lifecycle regressions exercise two fragments sharing one payload, compaction, partial deletion, tagged-snapshot retention, and final reclamation for top-level and nested Blob fields in formats 2.2 and 2.3. The metadata regression was reproduced against the original implementation in both Python-to-Rust and Rust-to-Python directions.
Related to #7274. This does not add automatic deduplication, cross-table ownership, or media semantics.