Skip to content

Commit fd8be32

Browse files
authored
Merge pull request #5510 from segmentio/update-retl-extract-schedule
update retl extract schedule
2 parents 24e8e06 + 9fad252 commit fd8be32

File tree

1 file changed

+17
-15
lines changed

1 file changed

+17
-15
lines changed

src/connections/reverse-etl/index.md

Lines changed: 17 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -96,32 +96,34 @@ To create a mapping:
9696
1. Navigate to **Conections > Destinations** and select the **Reverse ETL** tab.
9797
2. Select the destination that you want to create a mapping for.
9898
3. Click **Add Mapping**.
99-
2. Select the model to sync from.
100-
3. Select the **Action** you want to sync and click **Next**.
99+
4. Select the model to sync from.
100+
5. Select the **Action** you want to sync and click **Next**.
101101
* Actions determine the information sent to the destination. The list of Actions will be unique to each destination.
102-
4. In the **Select record to map and send** section, select which records to send to your destination after Segment completes extracting data based on your model. You can choose from:
102+
6. In the **Select record to map and send** section, select which records to send to your destination after Segment completes extracting data based on your model. You can choose from:
103103
* Added records
104104
* Updated records
105105
* Added or updated records
106106
* Deleted records
107-
5. Select a test record to preview the fields that you can map to your destination in the **Add test record** field.
108-
6. Select the **Schedule type** for the times you want the data to be extracted from your warehouse. You can choose from:
107+
7. Select a test record to preview the fields that you can map to your destination in the **Add test record** field.
108+
8. Select the Schedule type for the times you want the model’s data to be extracted from your warehouse. You can choose from:
109109
* **Interval**: Extractions perform based on a selected time cycle.
110110
* **Day and time**: Extractions perform at specific times on selected days of the week.
111-
7. Select how often you want the schedule to sync in **Schedule configuration**.
111+
9. Select how often you want the schedule to sync in **Schedule configuration**.
112112
* For an **Interval** schedule type, you can choose from: 15 minutes, 30 minutes, 1 hour, 2 hours, 4 hours, 6 hours, 8 hours, 12 hours, 1 day.
113113
* 15 minutes is considered real-time for warehouse syncs
114-
* For a **Day and time** schedule type, you can choose the day(s) you’d like the schedule to sync as well as the time. You can only choose to sync the extraction at the top of the hour.
115-
8. Define how to map the record columns from your model to your destination in the **Select Mappings** section.
116-
* You map the fields that come from your source, to fields that the destination expects to find. Fields on the destination side depend on the type of action selected.
117-
* If you're setting up a destination action, depending on the destination, some mapping fields may require data to be in the form of an object or array. See the [supported objects and arrays for mapping](#supported-object-and-arrays).
118-
9. *(Optional)* Send a test record to verify the mappings correctly send to your destination.
119-
9. Click **Save Mapping**.
120-
10. Select the destination you’d like to enable the mapping for under **Connections > Destinations > Reverse ETL**.
121-
11. Turn the toggle on for the **Mapping Status**. Events that match the trigger condition in the mapping will be sent to the destination.
114+
* For a **Day and time** schedule type, you can choose the day(s) you’d like the schedule to sync as well as the time.
115+
* You can only choose to start the extraction at the top of the hour.
116+
* Scheduling multiple extractions to start at the same time inside the same data warehouse causes extraction errors.
117+
10. Define how to map the record columns from your model to your destination in the **Select Mappings** section.
118+
* You map the fields that come from your source, to fields that the destination expects to find. Fields on the destination side depend on the type of action selected.
119+
* If you're setting up a destination action, depending on the destination, some mapping fields may require data to be in the form of an object or array. See the [supported objects and arrays for mapping](#supported-object-and-arrays).
120+
11. *(Optional)* Send a test record to verify the mappings correctly send to your destination.
121+
12. Click **Create Mapping**.
122+
13. Select the destination you’d like to enable on the **My Destinations** page under **Reverse ETL > Destinations**.
123+
14. Turn the toggle on for the **Mapping Status**. Events that match the trigger condition in the mapping will be sent to the destination.
122124
* If you disable the mapping state to the destination, events that match the trigger condition in the mapping won’t be sent to the destination.
123125

124-
To add multiple mappings from your warehouse to your destination, repeat steps 1-9 above.
126+
To add multiple mappings from your warehouse to your destination, repeat steps 1-13 above.
125127

126128
## Using Reverse ETL
127129
After you've followed [all four steps](/docs/connections/reverse-etl/#getting-started) and set up your source, model, destination, and mappings for Reverse ETL, your data will extract and sync to your destination(s) right away if you chose an interval schedule. If you set your data to extract at a specific day and time, the extraction will take place then.

0 commit comments

Comments
 (0)