I’m using

tap-mysql

(transferwise) with

LOG_BASED

replication, and filtering out a single column by removing it from the catalog file (I’ve also tried using the Meltano

select extra

and

schema extra

with the same result) which works as expected on the first load. But then returns this on subsequent loads:

time=2023-03-20 15:58:35 name=tap_mysql level=INFO message=Stream `stream-id`: Difference detected between event and schema: {'exclude_column'}
time=2023-03-20 15:58:35 name=tap_mysql level=INFO message=Stream `stream-id`: Running discovery ...

It seems to re-run discovery and then include the column I’ve set to exclude. Similar thread w/no response.

Is this https://github.com/transferwise/pipelinewise-tap-mysql/issues/50 ?

yes — this appears to be the same issue thankyou, so I think I can get around this by using the

--properties

flag. Going to test it out - I was thinking of

invoke

command facepalm , ended up using incremental replication method