Our Looker dashboard queries are hitting the raw tables instead of the aggregate tables today, so how do I force the persistent derived tables to rebuild immediately?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Our Looker dashboard queries are hitting the raw tables instead of the aggregate tables today, so how do I force the persistent derived tables to rebuild immediately?
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
Classifying 2 queries…
Searches and sources
ChatGPT2 real searches · gpt-6
Looker force rebuild persistent derived table immediately regenerator rebuild PDT admin page Google ↗
Looker aggregate awareness raw tables instead aggregate tables troubleshooting PDT rebuild Google ↗
- Derived tables in Looker | Google Cloud Documentation · docs.cloud.google.com
- Aggregate awareness | Looker | Google Cloud Documentation · docs.cloud.google.com
- Admin settings - Persistent Derived Tables | Looker | Google Cloud Documentation · docs.cloud.google.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Looker force rebuild persistent derived table immediately regenerator rebuild PDT admin page OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 | |
Looker aggregate awareness raw tables instead aggregate tables troubleshooting PDT rebuild OBSERVED | Google ↗ AI Mode ↗ | — | — | — | — | 1x of 1 |