Skip to content

Add info about Functions using Reverse ETL #6508

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Add info about Functions using Reverse ETL #6508

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
68735c5
Update index.md
vanand17 May 7, 2024
26dbb8c
Apply suggestions from code review
stayseesong Aug 29, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions src/connections/reverse-etl/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.