ktmud edited a comment on pull request #13306: URL: https://github.com/apache/superset/pull/13306#issuecomment-815125621
Oh, didn't notice you were reading datasets, charts, and dashboard metadata separately from three different API endpoints... Thought we'd still use `full_data` to bootstrap the Dashboard page. Then it would be a little tricky to persist (and properly clean) a backend cache for all three endpoints. I think the most expensive part of dashboard bootstrap data is checking dataset permissions, because it needs to run a separate SQL query to get the dataset info for each chart in the dashboard. If we can somehow make this process faster, then maybe a `full_data` cache is not necessary. Feel free to skip cache support for now and revisit later. -- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
