quickwit-oss / quickwit-oss/quickwit
Support compression of large gRPC messages directly in client/server
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
For potentially large messages such as ListIndexesMetadataResponse, IndexesMetadataResponse, etc., some fields are compressed/decompressed ad hoc. We would like the RPC framework to take care of that for us.
Since tonic does not support per method compression/decompression, one solution could be to rely on a custom Codec.
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 reviewing the existing ad hoc compression and decompression for large messages such as ListIndexesMetadataResponse and IndexesMetadataResponse. Then investigate tonic's per-method compression limitation and whether a custom Codec can move this responsibility into the RPC framework. Done means the client and server handle compression for these large gRPC messages without field-specific compression logic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, rust
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100