quickwit-oss / quickwit-oss/quickwit
Tracing: use pagination for queries fetching a huge number of spans
Open
Nobody has claimed this yet.
enhancement
tracing
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
I have implemented streaming spans ordered by trace ID in batches of size 1,000. However, regarding memory consumption, all the spans are still held in memory because we don't have a streaming search endpoint that allows sorting by a field (yet). An alternative solution would be to use pagination.
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 specific entry points are named. Start by locating the tracing query implementation and its span-fetching path, then inspect existing pagination support. Done means large span queries use pagination without retaining all spans in memory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- observability, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100