Skip to content

Commit 32d662a

Browse files
Apply suggestions from code review
1 parent 872922f commit 32d662a

File tree

1 file changed

+14
-11
lines changed

1 file changed

+14
-11
lines changed

src/connections/reverse-etl/system.md

Lines changed: 14 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -16,31 +16,34 @@ For Segment to compute the data changes within your warehouse, Segment needs to
1616
> warning ""
1717
> There may be cost implications to having Segment query your warehouse tables.
1818
19-
## Reverse ETL Schema
19+
## Reverse ETL schema
2020
When using Reverse ETL with Segment, several system tables are created within the `__segment_reverse_etl` schema in your warehouse. These tables are crucial for managing the sync process efficiently and tracking state information. Below are the details of the system tables in this schema:
2121

22-
**1. Records Table**
22+
### Records table
2323

24-
`records_<subscription_id>` table is located within the` __segment_reverse_etl` schema, this table contains two key columns:
24+
`records_<subscription_id>` table is located within the ` __segment_reverse_etl` schema.
2525

26-
`record_id`: A unique identifier for each record.
26+
This table contains two key columns:
2727

28-
`checksum`: A checksum value that is used to detect changes to a record since the last sync.
28+
- `record_id`: A unique identifier for each record.
29+
- `checksum`: A checksum value that is used to detect changes to a record since the last sync.
2930
The records table helps in determining new and updated rows by comparing the checksum values during each sync. If a record’s checksum changes, it indicates that the record has been modified and should be included in the next sync. This ensures that only the necessary updates are processed, reducing the amount of data transferred.
3031

31-
**2. Checkpoint Table**
32+
### Checkpoint table
3233

33-
The `checkpoints_<subscription_id>` tables are located within the __segment_reverse_etl schema, this table contains the following columns:
34+
The `checkpoints_<subscription_id>` tables are located within the __segment_reverse_etl schema.
3435

35-
`source_id`: Identifies the source from which the data is being synced.
36+
This table contains the following columns:
37+
38+
- `source_id`: Identifies the source from which the data is being synced.
39+
- `model_id`: Identifies the specific model or query that is used to pull data.
40+
- `checkpoint`: Stores a timestamp value that represents the last sync point for a particular model.
3641

37-
`model_id`: Identifies the specific model or query that is used to pull data.
38-
checkpoint: Stores a timestamp value that represents the last sync point for a particular model.
3942
The checkpoints table is used for timestamp-based checkpointing between syncs. This enables Segment to track the last successful sync for each model and avoid duplicating data when syncing, ensuring incremental and efficient data updates.
4043

4144
### Important Considerations
4245

43-
Do not modify or delete these tables: Altering or deleting the records and checkpoints tables can cause unpredictable behavior in the sync process. These tables are essential for maintaining the integrity of data during Reverse ETL operations.
46+
Do not modify or delete these tables. Altering or deleting the records and checkpoints tables can cause unpredictable behavior in the sync process. These tables are essential for maintaining the integrity of data during Reverse ETL operations.
4447
State management: The `__segment_reverse_etl` schema and its associated tables (records and checkpoints) manage the state of each sync, ensuring that only necessary data changes are synced and that the sync process can resume where it left off.
4548

4649

0 commit comments

Comments
 (0)