quickwit-oss / quickwit-oss/quickwit
Tiered Storage for Indexed Data
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
What: Tiered Storage for efficient live debugging and also to retain it long term
How: Store Index data to local disk or any block storage. Configure Snapshot to Cloud Storage (S3) periodically and allow expiration for both the indexed data.
Not aware of such features right now in Quickwit. But Elasticsearch does it very elegantly.
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
The issue names no files, tests, or entry points. Start by mapping Quickwit's existing index-storage and snapshot behavior, then review how local or block storage, periodic S3 snapshots, and expiration could fit together. Done means a defined, implemented, and tested tiered-storage design covering live access and long-term retention.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cloud, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100