Not sure if related to https://github.com/meltano/meltano/issues/8763, but I'm running into a strange issue where I filter out the streams using config so that they don't get included in the catalog at all. When I run the tap by itself using --discover, I can see that the generated catalog is correct. However, when running it as part of

meltano run

, I'm seeing the tap.properties.json created with the entire catalog visible. How does meltano call the tap when

meltano run

is called? Is it the singer sdk that creates that tap.properties.json, or is it meltano somewhere?

If you run meltano in debug mode it'll show the exact calls to discovery it's making

I filter out the streams using config

Maybe you're missing the same config when calling

meltano run

?

How does meltano call the tap when

meltano run

is called? Is it the singer sdk that creates that tap.properties.json, or is it meltano somewhere?

Meltano calls

<tap> --discover

in a subprocess, so it's a bit of both. Are you using tap-mssql?

I am using a custom fork of tap-mssql of wintersrd variant. I'm actually at a slight loss as to how it happens, because I cannot repro it with 100% success. I had already changed the executions to be synchronous, so it shouldn't be the parallelization issue from before.