Repository navigation
fix(blob): allow blob files across schema IDs - #460
Merged
Merged
Conversation
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.
Purpose
Linked issue: close #xxx
Blob files for the same field may span different schema IDs after schema evolution and normal file compaction.
Remove the schema ID consistency check from
BlobBunchwhile retaining the write-column consistency check.Tests
Added
BlobTableInteTest.TestBlobFilesAcrossSchemaIdsto simulate a post-compaction layout where one normal file bridges blob files written before and after schema evolution.API and Format
Documentation
Generative AI tooling
Generated-by: OpenAI Codex (GPT-5)