questdb / questdb/ui

Add query timeout setting to the Web Console

Open
#135 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Is your feature request related to a problem?

By default all SQL queries timeout after 60 seconds. While this is OK for the majority of them, sometimes there is a need to run longer queries, for example to copy tables.

Describe the solution you'd like.

Add a setting in the console to set the query timeout. Pass the timeout in each query header:

https://questdb.io/docs/reference/api/rest/#headers

This could be done in web console UI, after a user runs a query which hits a timeout. Consider the case in screenshot:

Screenshot 2023-05-12 at 16 00 11

At the bottom Log says timeout, query aborted [fd=104]. It would be useful to introduce some kind of a button to retry the query but with increased timeout limit.

Query used in screenshot:

CREATE TABLE readings AS(
  SELECT
    x ID,
    timestamp_sequence(
      to_timestamp('2019-10-17T00:00:00', 'yyyy-MM-ddTHH:mm:ss'),
      rnd_long(1, 10, 0) * 100000L
    ) ts,
    rnd_double(0) * 8 + 15 temp,
    rnd_long(0, 10000, 0) sensorId
  FROM
    long_sequence(100000000L) x
) TIMESTAMP(ts) PARTITION BY MONTH

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

Start in the QuestDB Web Console by tracing where SQL queries are sent, then consult the linked REST API headers documentation for the timeout header. The work is done when the console offers a timeout setting or retry path and passes the selected timeout with each query request.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
api, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.