*No plug and play*: When deciding for Meltano we t...
# singer-taps
t
No plug and play: When deciding for Meltano we thought we will safe a bunch of time since we could use existing singer taps or targets. However in 90% of the cases we needed to create a custom fork in order to either fix something or add basic functionality which was missing. Because of the other issues mentioned above this is sometimes a huge pain. So we are definitely not in a situation where you can easily just “use” certain taps
t
Would you be willing to share which tap / target combos you were having problems with?
t
Yeah definitely. So the target we use is target-bigquery from adswerve . The taps where we struggled and needed to customize / try to contribute: • tap-pardot (this is our fork with added docs and some enabling of extracting custom fields) • tap-postgres (this is our fork where we did some smaller improvements to the schema refresh and therefore selection) • tap-stripe (this is our fork where we fixed the schema selection based on the Meltano SDK code actually 🙂 . But chances that it gets merged into the official repo seems low) Hope that gives some context 🙂
t
yep - great context - thank you for sharing