[GitHub] [superset] graceguo-supercat commented on pull request #16674: fix: report with timeout chart

[GitBox <gi...@apache.org>]

graceguo-supercat commented on pull request #16674:
URL: https://github.com/apache/superset/pull/16674#issuecomment-918635722


   i like the idea about invalidate cache for report.
   - report cache and dashboard cache should be able to config separately.
   - I am not sure _retry_ can solve this problem. Let say i have a slow query taking 100 seconds to run. So webdriver trigger the query, after 60 seconds it got timeout exception, then the dashboard report will be hold for retry? When is the best time to trigger next try?
   - currently we have 60 second timeout, can we have extra config to allow query run longer? As a report, in my opinion, the queries should be verified and optimized, so that each chart should not longer than a limit. 60 second seems a little tough, maybe 120 seconds is good enough (without retry)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org