feat: readBlobRange — byte-range reads for O(1) point lookups#12
Merged
Conversation
…nt lookups FsBackend uses fs.read with file offset for true seek. Enables JSONL record stores where each record is read by seeking to its byte offset without parsing the full file. 5 new tests: start/middle/end of file, exact length, JSONL pattern.
- Validate offset/length non-negative, throw on negative values - Return only bytesRead bytes (not zero-padded buffer) when length exceeds file - Zero-length returns empty buffer immediately (no file I/O) - 4 new edge case tests: oversized length, zero length, offset at EOF, negative values
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.
Summary
readBlobRange(path, offset, length)— new method on StorageBackend for byte-range reads. FsBackend usesfs.readwith file offset for true O(1) seek.Breaking
readBlobRange.