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
We are trying to extend the query timeout for clickhouse queries beyond 5 minutes, but setting GUNICORN_TIMEOUT, SUPERSET_WEBSERVER_TIMEOUT has no effect, and setting timeout or connection_timeout in the SQLALCHEMY_ENGINE_OPTIONS via the UI gives an error: property is unknown or readonly
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
I have searched Superset docs and Slack and didn't find a solution to my problem.
I have searched the GitHub issue tracker and didn't find a similar bug report.
I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
The text was updated successfully, but these errors were encountered:
Bug description
We are trying to extend the query timeout for clickhouse queries beyond 5 minutes, but setting
GUNICORN_TIMEOUT
,SUPERSET_WEBSERVER_TIMEOUT
has no effect, and settingtimeout
orconnection_timeout
in theSQLALCHEMY_ENGINE_OPTIONS
via the UI gives an error:property is unknown or readonly
Screenshots/recordings
No response
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: