matt_cooley
12/16/2020, 5:50 AMtap-mysql
and target-postgres
(both pipelinewise variants) with replication-method=LOG_BASED
I have the following experience:
• First time it copies only the select:
columns (my understanding is this run is equivalent to replication-method=FULL_TABLE
)
• There’s a change to the upstream data (i.e. tap-mysql
)
• The next pipeline run copies every column (i.e. SELECT *
)
I’m pretty interested in the LOG_BASED
replication of explicitly selected columns. Not sure if this is a bug or something on my end, but I’ve been able to replicate a bunch of times on my end.
P.S. I’ve also been playing with FULL_TABLE
replication. It doesn’t recognize upstream deletes. Is that expected behavior? I didn’t think it was.
P.P.S. I’m guessing it’s gonna be Douwe responding. Thanks a bunch. Your responsiveness has been fantastic. Thank you.