limit offset could miss rows in hyperdx search.
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 9.9k
- Forks
- 471
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 117
Description
currently, the search ui use limit,offset to query clickhouse。
1，search last 1 minute, limit 200 to return 200 rows。
2，user scroll down。
3，search last 1 minute, limit 200,offset 200 to return more rows。
but the clickhouse not gurantee that same sql of limit offset is same。
if one Timestamp have more than one rows, it is possible to miss rows。
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
Trace the search UI's ClickHouse query and pagination path first, focusing on how rows are ordered across successive limit/offset requests. Reproduce the case with multiple rows sharing a timestamp, then verify that scrolling through pages returns every matching row without omissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, typescript
- Domain
- databases, frontend, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100