Hi everyone :slightly_smiling_face: . I’ve got a q...
# troubleshooting
b
Hi everyone 🙂 . I’ve got a question about the transferwise variant of the snowflake target (but it may apply to other targets also). I’ve got a stream which has a replication_method set to
FULL_TABLE
… my assumption was that when updating the target table in snowflake all rows would be deleted before the inserting the new rows. Instead a merge statement is used to add the new rows. This means that any records deleted from the source remain in the target table. Is this expected behaviour?
s
Not specific to your question but I know my postgres to postgres full_table replication does the same
b
Ah ok Steven, thanks good to know.
t
That is the expected behavior, at least by default., Check out the hard_delete option if you want deleted rows removed.
b
Ah ha Thomas! My hero 🙂. Exactly what i was looking for ❤️
s
I remember that not working for postgres, even though it should be supported. So your mileage may vary 🙂
t
Personally I prefer having the rows remain, with the sdc_deleted_at column populated... that way you can still see the old rows but they're easy to exclude.
b
Yes good shout, have gone with the
add_metadata_columns
option 👍
Ah unfortunately the options aren’t working after all 😞 (neither
hard_delete
nor
add_metadata_columns
) . It seems this is because the tap (tap-zendesk) doesn’t set a value for the _SDC_DELETED_AT property. Does anyone know a tap that does support the “Singer Data Capture” properties? I’m curious to see an example of when and how they are set…