matt_cooley
12/16/2021, 12:44 AMhard-deletes
in the source of my tap that I’m developing with the sdk. I’ve seen in the thread that ACTIVATE_VERSION
might be the way to go (vs. some custom logic checking the sdc_batched_at
columns for stale records).
First off, if someone has a better idea I’m all ears. If ACTIVATE_VERSION
is the way to go though I’m having some trouble wrapping my head around how to implement it in the SDK. Could someone point me to an example tap that uses ACTIVATE_VERSION
that might move along my understanding? Any hints on how it actually interacts with a target (I think it uses the operational columns?) OR how to tell if a target is compatible would also be rad. Thanks!aaronsteers
12/16/2021, 12:54 AMACTIVATE_VERSION
message is not yet supported in the SDK for taps. We are accepting merge requests and we have a description of the work to do here: Add support for ACTIVATE_VERSION message types (#18) · Issues · Meltano / Meltano SDK for Singer Taps and Targets · GitLabaaronsteers
12/16/2021, 12:56 AMmatt_cooley
12/16/2021, 1:00 AM_sdc_batched_at
(and extracted
) column, but I’ll get multiple timestamps for a “long” sync right? So I would just check for records within an interval (e.g. _sdc_batched_at >= max(_sdc_batched_at) - interval '12 hour'
)aaronsteers
12/16/2021, 1:46 AMmatt_cooley
12/16/2021, 2:01 AMdaniel_walker
12/16/2021, 9:28 AMaaronsteers
12/16/2021, 4:20 PMReuben (Matatika)
12/16/2021, 4:56 PM