quickwit-oss / quickwit-oss/quickwit
Refactoring: Remove the warmup procedure.
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Right now the warmup procedure is used to let us fetch our data asynchronously and use tantivy.
We can probably add a async search method that performs all of the fetch asynchronously and runs the compute in the Executor.
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 warmup procedure and tracing how it fetches data asynchronously and uses Tantivy. Review the Executor path and determine whether an async search method is the intended replacement. Done should mean the warmup procedure is removed, the replacement behavior is defined and implemented, and relevant search behavior remains covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- search
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100