From 3905b1948c1c20b15d6257b7396bdced8cd9eee1 Mon Sep 17 00:00:00 2001 From: joeynmq <37472597+joeynmq@users.noreply.github.com> Date: Tue, 19 Nov 2024 17:08:08 +0800 Subject: [PATCH 1/2] Update setup.md --- src/connections/reverse-etl/setup.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/connections/reverse-etl/setup.md b/src/connections/reverse-etl/setup.md index ba795eb770..3d8674d27a 100644 --- a/src/connections/reverse-etl/setup.md +++ b/src/connections/reverse-etl/setup.md @@ -50,6 +50,10 @@ Models define sets of data you want to sync to your Reverse ETL destinations. A ### dbt model Use Segment's dbt extension to centralize model management and versioning. Users who set up a BigQuery, Databricks, Postgres, Redshift, or Snowflake source can use Segment's [dbt extension](/docs/segment-app/extensions/dbt/) to centralize model management and versioning, reduce redundancies, and run CI checks to prevent breaking changes. +> warning "Limitation" +> Please be aware that if there are **5** mappings with a dbt Cloud schedule for a model, you will not be able to create additional mappings with the same dbt Cloud schedule type, regardless of the account or job selected. The limit applies per model. + + ## Step 3: Add a destination In Reverse ETL, destinations are the business tools or apps you use that Segment syncs the data from your warehouse to. A model can have multiple destinations. From 36fbeb533b3d3fb9baed08849066c5a98ef76b7a Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Wed, 18 Dec 2024 16:36:48 -0500 Subject: [PATCH 2/2] Update src/connections/reverse-etl/setup.md --- src/connections/reverse-etl/setup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/reverse-etl/setup.md b/src/connections/reverse-etl/setup.md index 3d8674d27a..c1a7a201ac 100644 --- a/src/connections/reverse-etl/setup.md +++ b/src/connections/reverse-etl/setup.md @@ -50,8 +50,8 @@ Models define sets of data you want to sync to your Reverse ETL destinations. A ### dbt model Use Segment's dbt extension to centralize model management and versioning. Users who set up a BigQuery, Databricks, Postgres, Redshift, or Snowflake source can use Segment's [dbt extension](/docs/segment-app/extensions/dbt/) to centralize model management and versioning, reduce redundancies, and run CI checks to prevent breaking changes. -> warning "Limitation" -> Please be aware that if there are **5** mappings with a dbt Cloud schedule for a model, you will not be able to create additional mappings with the same dbt Cloud schedule type, regardless of the account or job selected. The limit applies per model. +> success " " +> If you use dbt Cloud with Reverse ETL, you can [create up to 5 mappings](#step-4-create-mappings) that use the sync strategy **dbt Cloud**, which extracts data from your warehouse and syncs it with your destination after a job in dbt Cloud is complete. ## Step 3: Add a destination