quickwit-oss / quickwit-oss/quickwit
Use a metastore version number to avoid triggering scheduling when version is unchanged.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
The idea is incrementing a version number in the metastore on each change. We can then tag an indexing plan to a metastore version and just check if the plan version is the same as the one in the metastore to know if we need to schedule a new plan.
The metastore version should track only index/source config changes.
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 locating the metastore change handling, indexing-plan creation, and scheduling entry points. Define how a version changes only for index/source configuration updates, then verify that an indexing plan with the current metastore version does not trigger a new schedule while a changed version does.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100