Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QUERY_TIMEOUT_THRESHOLD change not working #3536

Closed
Manju106 opened this issue Sep 27, 2017 · 1 comment · Fixed by #3537
Closed

QUERY_TIMEOUT_THRESHOLD change not working #3536

Manju106 opened this issue Sep 27, 2017 · 1 comment · Fixed by #3537

Comments

@Manju106
Copy link

I tried changing the QUERY_TIMEOUT_THRESHOLD from 45000 to 120000, I have tried changing both in code and through export before starting the superset.

But again I am getting time out error in 45 sec . Is there any idea why the issue is ? And what is the possible way to increase my query timing

@Manju106 Manju106 changed the title QUERY_TIMEOUT_THRESHOLD change QUERY_TIMEOUT_THRESHOLD change not working Sep 27, 2017
@xrmx
Copy link
Contributor

xrmx commented Sep 27, 2017

QUERY_TIMEOUT_THRESHOLD has been removed, the client timeout is synced with the backend one SUPERSET_WEBSERVER_TIMEOUT in superset_config.py

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants