Looker is rebuilding PDTs on every single user query instead of caching the results; how do I fix the datagroup trigger settings to stop this?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
Looker is rebuilding PDTs on every single user query instead of caching the results; how do I fix the datagroup trigger settings to stop this?
1 real search · 1 real-search pass
Looker datagroup trigger PDT rebuild every query persist_with sql_trigger_value documentationGoogle ↗
OBSERVEDInstruction
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.
ChatGPT real searches (1)
Classes come from the query-classifier (a local Laya model). 1 of 1 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT1 real searches · gpt-6
Looker datagroup trigger PDT rebuild every query persist_with sql_trigger_value documentation Google ↗
- datagroup | Looker | Google Cloud Documentation · docs.cloud.google.com
- Admin settings - Datagroups | Looker | Google Cloud Documentation · 2.zoppoz.workers.dev
- datagroup_trigger | Looker | Google Cloud Documentation · docs.cloud.google.com
- Derived tables in Looker | Google Cloud Documentation · docs.cloud.google.com