quickwit-oss / quickwit-oss/quickwit
More defensive behavior when SourceCheckpoint is missing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Right now
- when apply a checkpoint to an existing that does not present any checkpoint in the metastore.
- when trying to resume a source that does not present any checkpoint in the metastore
We do not emit any error.
Instead we act as if there was an empty checkpoint.
This is not a bug but we could be more defensive.
One problem is that the ingest cli makes it rather difficult to fix.
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 ingest CLI paths for applying a checkpoint to an existing resource and resuming a source, then trace how missing checkpoints are read from the metastore. Review the surrounding error-handling behavior and the CLI's ability to surface recovery guidance. Done means missing SourceCheckpoint cases are handled defensively rather than treated as empty checkpoints, with a usable way to address the condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100