quickwit-oss / quickwit-oss/quickwit
Multi-tenant data model
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
-
tenant_id -
collection_id: a collection is a namespace for indexes and can hold configuration parameters common to all indexes: root URI, retention policy, transition policy, authorized groups and users, ...
Primary key for an index becomes: (tenant_id, collection_id, index_id)
Primary key for a split becomes: (tenant_id, collection_id, index_id, split_id)
We can migrate existing indexes to some default tenant and collection (_default?).
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
No files, tests, or entry points are named. Start by locating the index and split data-model definitions and the existing migration path, then determine how tenant and collection identifiers affect primary keys and collection-level configuration. Done means the new composite keys and migration to a default tenant and collection are fully specified and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100