@s is there anything i can do to help on the “it works” front?

• Work with Artem to resolve his build issues • Write an e2e test case for a scheduled sync (right now we only have manual sync)

cc @Michel since you were asking about this

The latest on postgres is right now we don't support incremental sync in our singer taps (ifaces do but impl doesn't account for it in a few places). That's the last remaining piece in postgres which then unblocks remaining e2e tests

impl as in the singer impl?

our data type is missing a key needed by singer (replication-key) and the type conversions don't account for it

@charles is replication-key input anywhere in the UI when setting up incremental sync?

no

aren’t just doing full refresh and append for MVP?

is replication key needed for append?

I thought we were just doing append

there's at least one point in the code where append was hard coded

you’re probably right.

the operative thing here is whether you need repication-key for append.

yeah

yes

singer only has

FULL_REFRESH

and

INCREMENTAL

whelp. we have a problem then.

the spec at least

how is replication key specified in singer? in the catalog?

yes

right next to where it specifies replication method

do you want to zoom about this real quick