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
Hey @berlicon! I'm here to assist you with any bugs, questions, and contribute to the repository. Let's tackle this issue together!
To resolve the "ClickHouse Connect (Superset) Error - expected string or bytes-like object" when executing the KILL QUERY command in Superset/SQL Lab connected to a ClickHouse database, ensure that the parameters passed to the command are of the correct type (string or bytes-like object).
Here's a code snippet to properly format the KILL QUERY command:
query_id="091f6bf3-18b4-4977-89e7-ac9a038a242f"# Ensure this is a stringkill_query_command=f"KILL QUERY WHERE query_id = '{query_id}'"# Execute the commanddatabase.execute(kill_query_command)
Make sure that query_id is a string. If query_id is obtained from another source, convert it to a string before using it in the KILL QUERY command.
If the issue persists, check the implementation of the execute method in your database connection to ensure it correctly handles the KILL QUERY command [1].
Bug description
I have error on Superset/SQL lab when tried to execute command:
KILL QUERY WHERE query_id='091f6bf3-18b4-4977-89e7-ac9a038a242f' -- GUID of my query
Error: "ClickHouse Connect (Superset) Error - expected string or bytes-like object"
Query Guid I can see in system.processes:
https://clickhouse.com/docs/en/operations/system-tables/processes
I can kill query with this sql command according to:
https://clickhouse.com/docs/en/sql-reference/statements/kill#kill-query
How to reproduce the bug
Screenshots/recordings
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: