Hi all, I'm trying to setup the tap-mysql transferwise variant to target-snowflake but encountering several issues/concerns: 1. New tables are not being reflected in the properties.json. Is the only solution to clear the

.meltano/run/tap-x

directory so it regenerates the catalog? 2. Our source systems add and remove new fields regularly so this is a big deal for us. How would Meltano cope with an existing field being deleted? 3. I’m currently running manual full table refreshes, will these behaviors also affect key based replication?

Hi 👋🏼 1. Yeah, it's a known edge case with fast-evolving source schemas: https://github.com/meltano/meltano/issues/6763 2. Singer targets (i.e. Meltano loaders) usually preserve columns, even when they're removed from the source and thus not included in the stream's schema in subsequent runs 3. Yes, this all still applies to incremental replication