Syncing the timeout param from backend

[mistercrunch]

Before, the client-side timeout was hard coded and not aligned with the backend's setting. You would have to recompile the JS bundle with a different value if you wanted to change it.

Now the value set in superset_config.py is sent to the client and the client will timeout regardless of it gets a web response or not.

fixes #3030 (I think?)

[coveralls]

Coverage remained the same at 69.397% when pulling 5abc0f690a7e02227d0e91155d56e3c53f04ced0 on mistercrunch:timeout_backend into 9f3aeb2 on apache:master.

[coveralls]

Coverage remained the same at 69.397% when pulling 5abc0f690a7e02227d0e91155d56e3c53f04ced0 on mistercrunch:timeout_backend into 9f3aeb2 on apache:master.

[coveralls]

Coverage remained the same at 69.388% when pulling cbd8cfd on mistercrunch:timeout_backend into a7ba6e4 on apache:master.

[xrmx]

A couple of late comments:

• docs/faq.rst needs update as it still references QUERY_TIMEOUT_THRESHOLD
• why a default is needed in superset/assets/spec/javascripts/sqllab/VisualizeModal_spec.jsx if we are reading it from the config? And if we need it why 45 and not 60 as the backend?

[andreineculau]

yup, I was going to make the same comment as @xrmx above - why is a default needed in the first place?

[mistercrunch]

2 - @andreineculau @xrmx it's a fixture for the unit test

[xrmx]

@mistercrunch Ah! missed the _spec in the name :)

[maxsonic]

@mistercrunch I got the timeout in the slice panel. It seems that the default timeout in the runQuery is 60s and it is not synced with the timeout set in the superset_config.py.

[xrmx]

@maxsonic that's a default, the caller should be updated

[tuziluobu]

What's the value which the client will timeout regardless of it gets a web response set in superset_config.py ？

[ghost]

Can anyone tell which is the new constant supplanting QUERY_TIMEOUT_THRESHOLD.

[xrmx]

SUPERSET_WEBSERVER_TIMEOUT

[ghost]

Thanks @xrmx . why this name got changed ?

[tuziluobu]

"Query timeout - visualization query are set to timeout at 60 seconds. Perhaps your data has grown, your database is under unusual load, or you are simply querying a data source that is to large to be processed within the timeout range. If that is the case, we recommend that you summarize your data further."

please How to resolve the problem？ I set SUPERSET_WEBSERVER_TIMEOUT=600 in superset_config.py,but It's not work。