From 1d8fb70ca9be8a1e482aa6376e1835357667f1d8 Mon Sep 17 00:00:00 2001 From: Olesia Date: Tue, 24 Oct 2023 15:30:44 -0400 Subject: [PATCH 1/2] Add information about delete records id --- src/connections/reverse-etl/index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/connections/reverse-etl/index.md b/src/connections/reverse-etl/index.md index 1e933ac5d5..a341a240ce 100644 --- a/src/connections/reverse-etl/index.md +++ b/src/connections/reverse-etl/index.md @@ -178,6 +178,9 @@ To get started with using Reverse ETL for subscriptions: ## Record diffing 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. + In order 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. > warning "" From 74dc946d8abbdd00bea03a33bd66e36901401ce3 Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Tue, 31 Oct 2023 09:11:20 -0700 Subject: [PATCH 2/2] Update src/connections/reverse-etl/index.md --- src/connections/reverse-etl/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/reverse-etl/index.md b/src/connections/reverse-etl/index.md index a341a240ce..d72391c052 100644 --- a/src/connections/reverse-etl/index.md +++ b/src/connections/reverse-etl/index.md @@ -179,7 +179,7 @@ To get started with using Reverse ETL for subscriptions: 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 its unique ID which can be accessed as `__segment_id`. In order 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.