Anybody have the skinny on how to 'trick' meltano/tap-postgres into using a custom value for

replication_key_value

? My use case here is that I'm replacing a legacy ELT pipeline and want meltano to resume where the previous one left off.

Hi, @edward_smith. I was just replying actually to your other thread. https://singer-io.slack.com/archives/C013J7TTTPX/p1619553931021700?thread_ts=1619550566.021600&cid=C013J7TTTPX I’m not sure if there’s a way to directly override the value without modifying a sample state output and then sending it back in an explicit state on the next run. Is this a date-type replication key by chance?

Lets chat over on singer slack since this probably applies to the tap more than meltano