Query time out in widget , not killing the query executing in database

[ambarishp]

We are currently using superset 4.1.2 . When the query time out in UI , the superset not sending query kill/cancel request to database, causing the query getting executed in db for long. Is there any configuration available to set the query kill timeout in superset

[dosubot[bot]]

Superset 4.1.2 does not have a configuration to automatically kill or cancel a running database query when a UI timeout occurs. Timeout settings like SQLLAB_TIMEOUT, SUPERSET_WEBSERVER_TIMEOUT, and SQLLAB_ASYNC_TIME_LIMIT_SEC control how long Superset waits for queries or results, but they do not send a kill/cancel request to the database if the UI times out—queries will continue running in the database unless manually stopped by the user (for example, by clicking STOP in SQL Lab) reference.

Some database engines (Hive, Impala, MySQL, SingleStore) have support for explicit query cancellation, but Superset only triggers these when the user cancels the query, not on timeout Hive, Impala, MySQL, SingleStore.

If you need queries to be killed after a certain duration, consider enabling asynchronous query execution and setting SQLLAB_ASYNC_TIME_LIMIT_SEC to limit how long queries can run before being killed by Celery (in async mode), but this is not tied to UI timeouts reference. There is currently no built-in way to automatically kill database queries on UI timeout in Superset 4.1.2.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}