Skip to content

Commit fff9c91

Browse files
committed
init commit
1 parent 31146f6 commit fff9c91

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

src/connections/reverse-etl/index.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -295,3 +295,10 @@ Column count | The maximum number of columns a single sync will process. | 512 c
295295
Column name length | The maximum length of a record column. | 128 characters
296296
Record JSON size | The maximum size for a record when converted to JSON (some of this limit is used by Segment). | 512 KiB
297297
Column JSON size | The maximum size of any single column value. | 128 KiB
298+
299+
## Reverse ETL Frequently Asked Questions
300+
301+
{% faq %}
302+
{% faqitem Why sync results constantly show "No records extracted", when "Updated records" is selected after I enabled the mapping? %}
303+
When "Updated Records" is selected and the values of query results (records) has not been changed after the first sync, then this situation is expected. During the first sync, reverse ETL system calculates a snapshot of all the resutls and creates records in `_segment_reverse_etl` schema. Therefore, all the rescords are considered as "Added records" instead of "Updated records" at this time. Thus, the records can only meet "Updated records" condition, when the underlying values changes after the first sync completes.{% endfaqitem %}
304+
{% endfaq %}

0 commit comments

Comments
 (0)