Enable partitioning for knowledge-bases to support multi-tenancy properly
Open
@vizsatiz is already working on this.
Since Aug 17, 2026.
- Dominant language
- Python
- Stars
- 200
- Forks
- 30
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 35
Description
For applications with multiple tenants, sharing an approximate index between tenants means vectors from one tenant can affect recall (and speed) for other tenants.
For tenant isolation, use list partitioning or separate tables.
CREATE TABLE items (customer_id int, embedding vector(3)) PARTITION BY LIST(customer_id);
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.