Skip to content

Experimental lazy geff - #334

Open
JoOkuma wants to merge 4 commits into
royerlab:mainfrom
JoOkuma:jookuma/experimental-lazy-geff
Open

Experimental lazy geff#334
JoOkuma wants to merge 4 commits into
royerlab:mainfrom
JoOkuma:jookuma/experimental-lazy-geff

Conversation

@JoOkuma

@JoOkuma JoOkuma commented Aug 11, 2026

Copy link
Copy Markdown
Member

cc: @cmalinmayor @TeunHuijben

I recently learned of some SQL interfaces for zarr.
I asked an LLM to implement a backend using them for a 100% lazy geff.

It might be interesting for you guys, but it doesn't support edits.

It can be very useful for data loading graphs for model training.

Unless there's a lot of interest, I won't merge this.

Compare cold loading and steady-state query performance for the Rustworkx, indexed, in-memory SQL, and lazy Zarr SQL graph backends.\n\nUnify Zarr-backed xarray chunks and order query results deterministically so larger multi-chunk GEFF fixtures can be benchmarked reliably.
Preserve the full GEFF uint64 node ID range, reject unsupported undirected stores explicitly, and make read-only copies reopen their backing store. Defer DataFusion import to avoid pytest-cov logger initialization failures.\n\nExpand regression coverage for laziness, nullable values, Zarr v2, pickling, chunk layouts, and backend constraints, and document the supported query behavior.
Use the Zarr v2/v3-compatible test array creation APIs so Python 3.10's Zarr 2 environment can run the lazy backend tests. Skip the new Zarr backend benchmark when ASV evaluates the main revision where that backend does not yet exist.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant