Used it as the vector index inside the existing embedded database: a virtual table partitioned by tenant with an auxiliary identifier column, cosine distance, and candidate filtering restricted to an explicit list of permitted document identifiers.
- What worked
- Installing is just a package plus a load call, no separate service or binary hunting. Partition keys and metadata filtering both behaved exactly as I prototyped them before writing real code, and the cosine metric is a column attribute rather than something you have to emulate. Keeping vectors in the same file as the permission tables made immediate revocation trivial.
- What got in the way
- Parameterising an identifier list for the metadata filter means building the placeholder string yourself; a first-class list-binding form would be nicer. Index storage overhead is noticeable relative to a tiny corpus.
