Skip to content

Add updated context re deleted records to RETL system page #7065

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

Merged
merged 2 commits into from
Sep 24, 2024
Merged

Add updated context re deleted records to RETL system page #7065

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
814b23c
add updates requested by eng
forstisabella Sep 24, 2024
d285eaa
Update src/connections/reverse-etl/system.md
forstisabella Sep 24, 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
2 changes: 1 addition & 1 deletion src/connections/reverse-etl/system.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ View reference information about how Segment detects data changes in your wareho
Reverse ETL computes the incremental changes to your data directly within your data warehouse. The Unique Identifier column is used to detect the data changes, such as new, updated, and deleted records.

> info "Delete Records Payload"
> The only value passed for deleted records is its unique ID which can be accessed as `__segment_id`.
> The only value passed for deleted records is their unique ID, which can be accessed as `__segment_id`. As of September 24, 2024, deleted records also contain all columns selected by your model, with `null` values in place of data.

For Segment to compute the data changes within your warehouse, Segment needs to have both read and write permissions to the warehouse schema table. At a high level, the extract process requires read permissions for the query being executed. Segment keeps track of changes to the query results through tables that Segment manages in a dedicated schema (for example, `_segment_reverse_etl`), which requires some write permissions.

Expand Down
Loading