Am I correct in assuming that currently it's impossible to implement a tap with the Meltano SDK that emits `ACTIVATE_VERSION`messages and annotates records accordingly? I've been grepping a bit and I'm mostly seeing some target-related logic and some settings parsing. Here's also a worringly-hardcoded

None

which strengthens my suspicion: https://github.com/meltano/sdk/blob/main/singer_sdk/streams/core.py#L879

I know there's an issue here https://github.com/meltano/sdk/issues/18 and a PR here https://github.com/meltano/sdk/pull/2686 Maybe that helps?

Thanks. Maybe I just need some rubberducking here... I'm writing a tap for our accounting software, and its REST API has endpoints like

/booked_invoices

,

/draft_invoices

,

/sent_invoices

. Instead of setting some

state

variable on an

/invoices

endpoint they simply disappear from the

draft

endpoint as soon as they've been booked. Obviously I'd like to properly detect that 😉

What I do (activate version would be better) is don't both implementing incremental replication (if possible it depends on data size) then

meltano run drop-tables tap-name target-name

done 🙂

Thanks, I'll look at that!