Connector Improvement: _fivetran_synced column for history
Hello, we are extracting incremental rows from a staging database populated by fivetran in history mode.
We are quite dissapointed that the row that gets 'expired' or inactive due to new update does not get the _fivetran_synced column updated to when the row was 'expired'
This would have been useful for us to pull incremental in DBT
Can this feature be made a installation or a connection parm?
The definition is this
-
_fivetran_synced(UTC TIMESTAMP) indicates the time when Fivetran last successfully synced the row.
-
Official comment
Hi Ramesh,
Thanks for your post here!
In history mode, we update the _fivetran_end column to when the record was made inactive. Would this address your use case?
When a record is updated in the source, in history mode the previous version will have it's _fivetran_end column set to the time of the new version's update, and the new version will have a new _fivetran_start timestamp.
Please sign in to leave a comment.
Comments
1 comment