Update warehouse-connectors.mdx (#1693)

mixpanel · Dec 19, 2024 · 66ef878 · 66ef878
1 parent d803a2b
commit 66ef878
Showing 1 changed file with 4 additions and 0 deletions.
diff --git a/pages/docs/tracking-methods/warehouse-connectors.mdx b/pages/docs/tracking-methods/warehouse-connectors.mdx
@@ -499,6 +499,10 @@ which uses [column mappings](https://docs.databricks.com/en/delta/delta-change-d
 
 <Tabs.Tab>
 
+<Callout type="warning">
+  Redshift Mirror is currently in beta.
+</Callout>
+
 Mirror takes Redshift table snapshots and runs queries to compute the change stream between two snapshots using the computed MD5 hash value for each row. Snapshots are stored in a staging schema created in [Step 1](#step-1-connect-a-warehouse).
 - If two rows in Redshift table are identical across *all* columns, the md5 hash value Mirror computes for each row will be the same and Mixpanel will consider them the same row causing only one copy to appear in Mixpanel. We recommend ensuring that one of your columns is a unique row ID to avoid this.
 - The table snapshots managed by Mixpanel and are automatically cleaned-up. Under normal conditions, Mirror maintains only one snapshot per-sync and removes the older run's snapshot as soon as it has been used by the subsequent sync run. These snapshots will incur some additional storage cost.