questdb / questdb/ui

Wrong Number of Rows is Presented When Using LIMIT with LT JOIN Queries

Open
#164 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

web-console
Dominant language
TypeScript
Stars
29
Forks
39
Avg merge
4d 11h
Merged PRs (30d)
4

Description

On my example actual rows amount is 1300.
image

Contributor guide

No contributing guide indexed for this repository

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

The report includes only a screenshot and says that a LIMIT query using LT JOIN displays the wrong row count. Start by reproducing the example and comparing the displayed count with the actual 1,300 rows; the payload does not identify an entry point, file, or test. Done means the UI presents the correct count for this query, with a regression test if the relevant test location is found.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.