You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
SQL Lab has Stop button but it only updates state of superset without actually stopping the database query. Leaving the queries running in the background affect database performance.
Running queries should be killed automatically in the database if the stop button pressed, the browser window closed or navigated to another site.
Describe the solution you'd like
Pressing the stop button in SQL Lab should trigger a mechanism to kill the running query in the database. The same function should be called when the browser windows closed or navigated to another site.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered:
koszti
changed the title
[sqllab] Stop button should kill/cancel running query in the database
[sqllab] Stop button should kill running query in the database
Jun 27, 2021
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.
Is your feature request related to a problem? Please describe.
SQL Lab has Stop button but it only updates state of superset without actually stopping the database query. Leaving the queries running in the background affect database performance.
Running queries should be killed automatically in the database if the stop button pressed, the browser window closed or navigated to another site.
Describe the solution you'd like
Pressing the stop button in SQL Lab should trigger a mechanism to kill the running query in the database. The same function should be called when the browser windows closed or navigated to another site.
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: