From 68735c552e6aad33d307b9490cd74889b0a064b2 Mon Sep 17 00:00:00 2001 From: vanand17 <96406241+vanand17@users.noreply.github.com> Date: Tue, 7 May 2024 15:59:45 +1000 Subject: [PATCH 1/2] Update index.md --- src/connections/reverse-etl/index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/connections/reverse-etl/index.md b/src/connections/reverse-etl/index.md index e21d4921b3..f069de5570 100644 --- a/src/connections/reverse-etl/index.md +++ b/src/connections/reverse-etl/index.md @@ -342,3 +342,8 @@ In case of consecutive failures, Segment sends notifications for every sync fail #### Can I have multiple queries in the Query Builder? No. In Reverse ETL, Segment executes queries in a [common table expression](https://cloud.google.com/bigquery/docs/reference/standard-sql/query-syntax#with_clause){:target="_blank”}, which can only bind the results from **one single** subquery. If there are multiple semicolons `;` in the query, they'll be treated as several subqueries (even if the second part is only an inline comment) and cause syntax errors. + +#### Can I use functions with Reverse ETL? +Functions aren't yet supported by the Reverse ETL pipeline. As a workaround, instead of using the [Segment Connections](https://segment.com/docs/connections/destinations/catalog/actions-segment/) integration, you could instead use the [Webhook (Actions)](https://segment.com/docs/connections/destinations/catalog/actions-webhook/) integration behind your Reverse ETL extraction. With that in place, you can send data to a [Source Functions](https://segment.com/docs/connections/functions/source-functions/). You can write the code in that Function to do the work you had wanted to do in the Insert Function. From there, whatever data your code allows to move on will flow into a Segment source just like it would if you were using Segment Connections. + +The pipeline here would be Reverse ETL model → Webhook (Actions) → Source Function → Segment source. From 26dbb8ccef7cacaf6517a5d721454deedf649205 Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Thu, 29 Aug 2024 07:53:34 -0700 Subject: [PATCH 2/2] Apply suggestions from code review --- src/connections/reverse-etl/index.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/connections/reverse-etl/index.md b/src/connections/reverse-etl/index.md index f069de5570..c185b4885d 100644 --- a/src/connections/reverse-etl/index.md +++ b/src/connections/reverse-etl/index.md @@ -344,6 +344,5 @@ In case of consecutive failures, Segment sends notifications for every sync fail No. In Reverse ETL, Segment executes queries in a [common table expression](https://cloud.google.com/bigquery/docs/reference/standard-sql/query-syntax#with_clause){:target="_blank”}, which can only bind the results from **one single** subquery. If there are multiple semicolons `;` in the query, they'll be treated as several subqueries (even if the second part is only an inline comment) and cause syntax errors. #### Can I use functions with Reverse ETL? -Functions aren't yet supported by the Reverse ETL pipeline. As a workaround, instead of using the [Segment Connections](https://segment.com/docs/connections/destinations/catalog/actions-segment/) integration, you could instead use the [Webhook (Actions)](https://segment.com/docs/connections/destinations/catalog/actions-webhook/) integration behind your Reverse ETL extraction. With that in place, you can send data to a [Source Functions](https://segment.com/docs/connections/functions/source-functions/). You can write the code in that Function to do the work you had wanted to do in the Insert Function. From there, whatever data your code allows to move on will flow into a Segment source just like it would if you were using Segment Connections. +Functions aren't supported by Reverse ETL. As a workaround, instead of using the [Segment Connections](/docs/connections/destinations/catalog/actions-segment/) integration, use the [Webhook (Actions)](/docs/connections/destinations/catalog/actions-webhook/) integration behind your Reverse ETL extraction. With that in place, you can send data to [Source Functions](/docs/connections/functions/source-functions/). You can write the code in that function to do the work you had wanted to do in the Insert Function. From there, the data your code allows to move on, flows into a Segment source just like it would if you were using Segment Connections. -The pipeline here would be Reverse ETL model → Webhook (Actions) → Source Function → Segment source.