Register FOOTNOTE as a CloudVectorIndex driver (make footnote default)#2
Open
jlocala1 wants to merge 2 commits into
Open
Register FOOTNOTE as a CloudVectorIndex driver (make footnote default)#2jlocala1 wants to merge 2 commits into
jlocala1 wants to merge 2 commits into
Conversation
Adds @mieweb/footnote as a local vector driver — exactly the extension the registry
docs describe ('adding a new backend … is a registerDriver() call'). footnote is the
richer Vectorize-compatible store (hybrid + FTS + assertion-aware retrieval) that
cloud's own sqlite-vec adapter already mirrors; this wires in the real one.
- vendor/footnote: git submodule (mieweb/melvil-artipod-footnote @ main)
- cloud-local: link: dep on @mieweb/footnote (kept out of the workspace so recursive
scripts are unaffected)
- registry.mjs: registerDriver('footnote', …) wrapping footnote's shipped createLocalIndex
Self-contained — no footnote-side change needed. Verified: driver registers and
upsert/query work through cloud at runtime; tsc --noEmit clean. Additive +
backward-compatible (existing 'sqlite-vec' configs still work).
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
The conformance suite exercised the Vectorize contract only against
sqlite-vec; the footnote driver registered by the 'make footnote default'
change had no coverage. Add a matching case that resolves a
{ driver: 'footnote' } binding through createCloudEnv + settleEnv (the real
mieweb.jsonc path) and asserts upsert/query/$eq+$in filter/delete. Skips
cleanly when @mieweb/footnote isn't linked.
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
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.
What
Registers
@mieweb/footnoteas a localCloudVectorIndexdriver, so it can be thedefault vector store instead of cloud's own
sqlite-vecadapter.This is exactly the extension the registry documents:
Why
cloud's
vectorize-sqlitevecadapter already mirrors the FOOTNOTE index pattern (its owncomment says so). footnote is the real thing — same Vectorize-compatible contract, plus
hybrid + FTS + literal search and validated negation/assertion-aware retrieval. This
consolidates onto it.
Changes
vendor/footnote— git submodule (mieweb/melvil-artipod-footnote @ main)packages/cloud-local/package.json—link:dep on@mieweb/footnotepackages/cloud-local/src/registry.mjs—registerDriver('footnote', …)wrapping footnote'screateLocalIndexAdditive + backward-compatible — existing
sqlite-vecconfigs still work.How to make it the default
Point a vector binding at it in
mieweb.jsonc: