Yeah @todd_de_quincey
The bugs weren't edge case bugs either IMO. They were major issues in both the bigquery destination and salesforce source which happened to be the two I needed during PoV after already pitching an architecture diagram.
One bug cause salesforce source to fail and tip over on an undecodable byte despite salesforce documentation stating the two possible encodings as they were assuming 1. It would leave trash temp tables in the database too. A lot of them since it defaulted to automatically retry 3 times. Mind you on an initial salesforce sync it was SLOW. 7+ hours slow. Insane. I wrote some async python to do it in sub 15 minutes in a day.
The bigquery bug was even more ridiculous considering an update essentially bricked the connector. A json schema validation fails relating to loading to GCS staging. I don't actually think this one is fixed, but obviously the integration testing is lacking some surface area.
Outside these bugs, the performance is bad, the overhead is high, 2.5K issues and rising on github is concerning, their slack is full of posts (maybe 75% or more) on issues/bugs instead of good conversation, these issue posts are always met with a "please post this on our discourse", and lastly if memory consumption is too high, the worker pods literally hang indefinitely.
I get it, they are alpha -- I also get it that it open source. But they really make out this whole position like they are ready to be thrown up in your production environment with a few minutes of set up. I wasted a week on bugs in what you would think are 2 highly trafficked connectors. Meltano on the other hand, again, just worked.