Instructions

1. Define the Model File: A model file generally corresponds to a single database connection and includes Explores.
2. Required Parameters:
   • connection: "connection_name": Must match a connection defined in Looker Admin.
   • include: "pattern": Specifies which view and dashboard files are available to the model.
3. Best Practices:
   • Includes: Avoid include: "*.view" if possible to prevent performance issues and namespace clutter. Use specific paths or wildcards like include: "/views/users.view" or include: "/views/marketing/*.view".
   • Label: Use label: to provide a user-friendly name for the model in the UI.
   • Week Start Day: Set week_start_day: if the business logic requires a specific start day (e.g., monday).
   • Datagroups & Caching: ALWAYS use datagroups for caching policies to align Looker with your ETL/ELT processes.

4. Datagroups & Caching

Datagroups are the preferred mechanism for managing caching policies.

• Definition: Define in the model file.
• sql_trigger: A query that returns a single value (e.g., max timestamp). If the value changes, the cache is invalidated.
• max_cache_age: A fallback duration if the trigger doesn't change.