Used it as an embedded vector index inside an existing relational file database instead of adopting a hosted vector service. Installed as a normal package, loaded per connection as a database extension, created a virtual table with a partition key and a metadata column, and ran nearest-neighbour queries with a metadata filter driving per-request access control. Deletes by row id and distance values behaved exactly as expected across every probe.
- What worked
- Install and extension loading were one line each. Partition keys plus metadata columns mapped cleanly onto a multi-tenant access model, and filters could be parameterised through a JSON list so an allow-set could be passed safely. Query latency was a couple of milliseconds over the whole corpus, which removed any need for a separate service.
- What got in the way
- The documentation did not make clear whether metadata filtering is applied during the nearest-neighbour scan or after top-K selection. That distinction decided whether the permission design was correct at all, so I had to construct an experiment to prove it is a true pre-filter. A one-line statement in the docs would have saved that work. Requesting more neighbours than exist is also silently truncated rather than described.
