From fa1cc2f6caf4e5df4036caf372670610a6490357 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Thu, 2 Apr 2026 12:23:18 +0000 Subject: [PATCH] Reduce redundancy between granularity bullet and tip Generated-By: mintlify-agent --- references/pre-aggregates/overview.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/references/pre-aggregates/overview.mdx b/references/pre-aggregates/overview.mdx index a482355e..8ce819ee 100644 --- a/references/pre-aggregates/overview.mdx +++ b/references/pre-aggregates/overview.mdx @@ -74,10 +74,10 @@ When a user runs a query, Lightdash automatically checks if a pre-aggregate can - Every dimension used in **filters** is included in the pre-aggregate - All metrics use [supported metric types](#supported-metric-types) - The query does not contain custom dimensions, custom metrics, or table calculations -- If the query uses a time dimension, the requested granularity is **equal to or coarser** than the pre-aggregate's granularity (for example, a `day` pre-aggregate can serve `day`, `week`, `month`, or `year` queries, but not `hour`) +- If the query uses a time dimension, the requested granularity must be **equal to or coarser** than the pre-aggregate's granularity - If you pre-aggregate at **day** granularity, the cache hits for `day`, `week`, `month`, `quarter`, and `year` queries. If you pre-aggregate at **month** granularity, the cache hits for `month`, `quarter`, and `year` — but **not** for `day` or `week`, since those require finer-grained data. + A **day** pre-aggregate serves `day`, `week`, `month`, `quarter`, and `year` queries. A **month** pre-aggregate serves `month`, `quarter`, and `year` — but **not** `day` or `week`, since those need finer-grained data. When multiple pre-aggregates match a query, Lightdash picks the smallest one (fewest dimensions, then fewest metrics as tiebreaker).