deepset-ai / deepset-ai/haystack-core-integrations
Weaviate: Consider Adding support for multi tenancy
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 203
- Forks
- 332
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 80
Description
Is your feature request related to a problem? Please describe.
Weaviate supports adding multi tenancy which is useful in certain use cases e.g. large scale deployments, e-commerce
Describe the solution you'd like
specify tenant when doing CRUD ops with the WeaviateVectorStore
Describe alternatives you've considered
NA
Additional context
- docs on multi tenancy in weaviate
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.
Research direction
Start by reviewing the linked Weaviate multi-tenancy documentation and locating the WeaviateVectorStore CRUD integration. Define how a tenant is supplied for create, read, update, and delete operations. Done means CRUD operations can target a specified tenant without breaking existing usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100