Repository navigation
fix(csr): stream high-degree expansion in bounded chunks - #31
Merged
Merged
Conversation
Resolve #11 by resuming neighbor traversal between output batches and storing immutable deletion occurrence offsets. Add focused traversal/snapshot tests, a reusable hub memory scenario, and documentation. Assisted by Codex.
prrao87
marked this pull request as ready for review
October 26, 2026 16:14
Deploying lance-csr with
|
| Latest commit: |
4af666a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6fc05a63.lance-csr.pages.dev |
| Branch Preview URL: | https://codex-issue-11-inline-local.lance-csr.pages.dev |
This was referenced Oct 26, 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.
Problem and change
Resolves #11. CSR expansion emits bounded output chunks while retaining a resumable neighbour position, rather than collecting the complete fan-out and output. Deleted occurrences use snapshot offsets; duplicates, self-loops, missing targets, filtering, errors and existing-reader snapshots preserve their semantics.
The cursor borrows adjacency slices at the saved offset. Counters stay local until a chunk returns, and the three tiny live-neighbour constructors inline at the traversal boundary. This removes the measured per-edge abstraction overhead without changing deletion semantics. Deletion refresh still scans affected sources to resolve immutable offsets.
Validation
Head
d7ad39819d04acf44907213ba7532df5e93d8869; frozen parent54e02307a48e467a98d9da2183f5adcb767e7c99. Focused checks and regression details record commands, results, documentation and compatibility. The release receipt pins wheel/archive identity and 110 installed tests.Both complete workloads pass unchanged goldens in memory and lazy modes. Retained first-pass geometric mean speedups are below (greater than one is faster). Per-query results and paired investigations remain in the audit archive.
Measurements use the same Apple M4 Max (16 cores, 128 GiB), macOS 26.6.2 arm64 and Python 3.13.17, with Q30 revision
6260689and IC revisionc185123. Reproduction instructions pin settings, data checksums, locks and commands. The frozen main baseline is code-identical to current main90114f3; the equivalence check also verifies clean prospective main-target merges.Individual review gates pass under the recorded repeat/controlled-investigation rules. Initial failed measurements remain intact in the audit record.
User impact
Expansion yields bounded chunks; deletion refresh resolves occurrence offsets by scanning affected sources. CSR docs describe per-partition memory bounds and the wide-property benchmark. Python signatures are unchanged.
Review ledger · Current contribution guide
Audit archive: 47,675,190 bytes; SHA-256
b3486fb30a34639c830b5d49353b3838f96369f95df959ac35f85511f7f8b2de. The small current-main supplement preserves the documentation update. Original absolute paths in receipts map to included records through the archive index.Submitted by David Hughes (@stugorf), with AI Collaboration.