It seems the Meltano run command doesn't refresh the catalog, is it by design? If the schema changes, we have to run the Invoke or select to get the latest schema? I want to automatically copy all existing and future columns by selecting dbo-mytable.*, but the new column is not automatically discovered.

Hi, @lidong_zhao. This is a known issue, especially for database taps which are subject to frequent changes. We have an issue and feature request to add more control to the caching process. The suggested workaround in the meanwhile is to manually delete the cached catalog.json file from the .meltano subdirectory, which will force a refresh upon the next run.

Thanks.