quickwit-oss / quickwit-oss/quickwit

Consider different nodes for search and doc fetching

Open
#329 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

backlog enhancement low-priority
Dominant language
Rust
Stars
11.7k
Forks
597
Avg merge
2d 22h
Merged PRs (30d)
37

Description

Currently the same nodes which are used for searching are used to retrieve documents.
This is done in order to hit caches, but the caches for searching and document fetching are mostly disjunct, so it should be possible to have a different set of nodes for document retrieval and for search in order to be able to spread the load further.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating where the same nodes are selected for search and document retrieval, then trace how caching influences that choice. Done should mean search and document fetching can use distinct node sets while preserving the intended behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
distributed-systems, search
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.