Skip to content

Commit 72732d5

Browse files
Merge pull request #7065 from segmentio/delete-records-payload-update
Add updated context re deleted records to RETL system page
2 parents 743d4d9 + d285eaa commit 72732d5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/connections/reverse-etl/system.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ View reference information about how Segment detects data changes in your wareho
99
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.
1010

1111
> info "Delete Records Payload"
12-
> The only value passed for deleted records is its unique ID which can be accessed as `__segment_id`.
12+
> 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.
1313
1414
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.
1515

0 commit comments

Comments
 (0)