Repository navigation
docs: warn early that string and uuid keys slow traversal - #138
Merged
Merged
Conversation
Add an integer-key tip where the first graph is defined, give the key section in Graph schema a performance-oriented heading, and spell out the integer-key case and the benchmark key types on the CSR page.
Deploying lance-csr with
|
| Latest commit: |
aaf3e0c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://dd886ee5.lance-csr.pages.dev |
| Branch Preview URL: | https://docs-integer-key-performance.lance-csr.pages.dev |
prrao87
marked this pull request as ready for review
November 7, 2026 14:38
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.
Why
The CSR index only works with integer keys. With string or UUID keys,
use_csr=Truesilently falls back to hash joins over whole tables at every hop. The query returns the same results but runs slower, and nothing warns the user. The docs said this, but only in a short tip late in Getting started ("anything else quietly uses joins"), under a Graph schema heading that doesn't mention performance, and on the CSR page. A user picking key types for a new graph could easily miss it until queries were already slow.What changed
Validation
uv run --project docs --locked zensical build --strict: no issues, and the new cross-page anchor resolves.uvx typos@1.26.0 .: clean.csr_stats()is empty and plain hops plan as joins with no warning. A path variable query raisesNotImplementedErrorwithuse_csron and off.🤖 Generated with Claude Code