quickwit-oss / quickwit-oss/quickwit
Add split boundary/partition policy
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
We want the ability to add some constraints on the bounds of the splits that Quickwit produces. For instance, a daily split boundary policy would ensure that splits do not span across multiple days.
To do
- Naming (boundary, partition, ...)
- Spec how index config declares policy
- Ensure indexer starts a new split each time a boundary is crossed
- Ensure splits are not merged across boundaries
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 tracing the index config, indexer split creation, and split-merging paths described in the issue. Clarify the boundary or partition naming and configuration shape, then verify that a boundary starts a new split and prevents merges across it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100