michael-s-molina commented on issue #20300: URL: https://github.com/apache/superset/issues/20300#issuecomment-1181662441
> Currently, like shown in this SIP, we're saving the tokens to the metadata db, in hindsight, I suggest adding the option to save them to the cache instead, since they expire anyway and to avoid multiple trips to the DB to fetch them throughout the period the user is querying the data source. @betodealmeida If we choose to use the cache to store this information, our [custom flask caching backend](https://github.com/apache/superset/pull/19232) can store data in the `key_value` table in case a client does not support any of the available [backends](https://flask-caching.readthedocs.io/en/latest/#built-in-cache-backends) 😉 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
