GitHub user rusackas added a comment to the discussion: Hiding Force refresh in 
Dashboard

Sounds reasonable, but just to play devil's advocate here... are you sure you 
have a lot of users doing "force refresh" or is the dashboard's cache timeout 
too short? Also _maybe_ worth noting that people can still run these queries 
via the chart builder or SQL lab views as frequently as they want. 

Another solution would be to put a tool in the middle that queries athena on a 
schedule (or provides an additional layer of caching, at least), keeping the 
resulting data in a more cost-effective warehouse/lake/db/etc. which you'd 
connect Superset to.

GitHub link: 
https://github.com/apache/superset/discussions/32806#discussioncomment-12589416

----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: 
notifications-unsubscr...@superset.apache.org


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

Reply via email to