quickwit-oss / quickwit-oss/quickwit
Reduce size of field caps gRPC messages
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Quoting @PSeitz and @fulmicoton:
We should limit the number of fields returned, if the key is actually data e.g.
{"<some_id>": true}, we probably should not return it. Ideally, we would detect which fields are relevant and which are not.
+1 on scoring the fields and returning a top K. The best signal would probably:
- in schema or not
- if we can grab that info, how many docs have the field or not
- field name length
- does the field name contain weird characters or not, etc?
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
No files, tests, or entry points are identified. Start by locating the gRPC response construction and existing field-cap behavior, then determine how field relevance and a top-K limit should be defined. Done means the messages return only the intended relevant fields with a documented, testable selection rule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100