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
When the SQL statement is mis-configured, a large output might generated (which waste plenty of time and resource). Is it a good idea to handle keyboard interrupt (e.g. Ctrl + C) and cancel the corresponding query if it is still running on Athena? I can work on this feature if you think it is appropriate.
The text was updated successfully, but these errors were encountered:
When the SQL statement is mis-configured, a large output might generated (which waste plenty of time and resource). Is it a good idea to handle keyboard interrupt (e.g. Ctrl + C) and cancel the corresponding query if it is still running on Athena? I can work on this feature if you think it is appropriate.
The text was updated successfully, but these errors were encountered: