From 4e6674311404ad12bbdbcbcfe915e1e196ede43e Mon Sep 17 00:00:00 2001 From: AK Date: Tue, 26 Aug 2025 10:12:25 -0400 Subject: [PATCH] Add note about BigQuery ingestion time partitions internal discussion: https://mixpanel.slack.com/archives/C04E6U2NN1X/p1756130022552739 --- pages/docs/tracking-methods/warehouse-connectors.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/pages/docs/tracking-methods/warehouse-connectors.mdx b/pages/docs/tracking-methods/warehouse-connectors.mdx index 277bb61026..124d768221 100644 --- a/pages/docs/tracking-methods/warehouse-connectors.mdx +++ b/pages/docs/tracking-methods/warehouse-connectors.mdx @@ -583,6 +583,8 @@ To understand the potential savings consider a 100 GB source table with 100 days - If this table is not partitioned and is synced daily the Append sync will scan the whole table (100 GB of data) each time it runs, or 3,000 GB of data per month. - If this table is partitioned by day and is synced daily with an Append sync the Append sync only scan the current day and previous day's partitions (2 GB of data) each time it runs, or 60 GB of data per day, a 50x improvement over the un-partitioned table. +Note: [BigQuery's ingestion time partitions](https://cloud.google.com/bigquery/docs/partitioned-tables#ingestion_time) **are not supported** in Append mode. + --- ### Full