![]() When all the charts on the current page are being served from the cache, you'll see a lightning bolt icon along with the time and date of the last update. You can see if data is coming from the cache by viewing the report and looking in the bottom left corner. This refreshes the cache for every data source added to the report. In the top right, click and then click Refresh data.Report editors can refresh the cache at any time: This includes queries that bypass the cache, as well as manual and automatic cache refreshes. New queries generated by components on the report go directly to the underlying platform and the responses are added to the cache for those components.īigQuery users: please be aware that the usual query costs will apply whenever Looker Studio queries the underlying project. When the cache refreshes, all the old cached data and remembered queries are discarded. The results of that new query are then added to the table's cache, and Looker Studio remembers the new query for future use. For example, if a viewer changes the date range or filters the table described above by a new country, then Looker Studio requests the new data from the underlying data set. If the request can't be served from the cache, Looker Studio requests the data from the underlying data set. When a component in your report requests data, if that query matches a previously received query, then the new data request is served from the cache. The results of this query are cached for this particular scorecard. The underlying query for the scorecard would be something like SELECT SUM(revenue) FROM (SELECT * FROM tableName). Now, in your report, you add a scorecard with the metric SUM(revenue). The results of this query are not cached, since the cache applies to charts and components, not the data source as a whole. Let's say your data source connects to a custom SQL query: SELECT * FROM tableName. ![]() For example, the cache for a table with 2 dimensions and 3 metrics, having a default date range of the last 28 days, and filtered by some value (country = Belgium, for instance) will contain only the data needed to display that table. That cache contains only the data needed to create that component's default visualization. How the cache worksĮvery component in a Looker Studio report has its own individual cache. Report editors can also manually refresh the cache (see below).
0 Comments
Leave a Reply. |