For every star on GitHub, we'll donate $2 to clean up our waterways. Star us now!
Discoverable plugins that are supported out of the box are available in Meltano Hub.
If you’ve added a custom plugin (or variant) to your project that could be discoverable and supported out of the box for new users, please contribute its description to Meltano Hub to save the next user the hassle of setting up the custom plugin. GitHub makes it easy to contribute changes without requiring you to leave your browser.
Discoverable plugin definitions in Meltano Hub have the a very similar format as custom plugin definition in your meltano.yml project file, so a copy-paste is usually sufficient.
The format and further requirements are laid out in more detail in the Meltano Hub plugin definition syntax document.
When the maintainer of the default variant of a discoverable plugin becomes unresponsive to issues and contributions filed by the community, that plugin is considered up for adoption, which means that we are looking for a different variant of the plugin with a more engaged maintainer to become the new default.
This new variant can either be a fork of the original default variant, or an alternative implementation for the same source or destination, as long as it is actively maintained.
If you maintain or are aware of such a variant, please add it to your Meltano project as a custom plugin and make it discoverable, or file an issue so that the Meltano core team can assist you.
As a plugin’s primary maintainer, you do not have to spend a lot of time improving the plugin yourself. In fact, attracting more users and getting the community involved is likely to recude your personal maintenance burden, since you’ll receive contributions with bug fixes and new features that you will only be expected to review, not build yourself.
We should be good citizen about these, and use the default workflow to contribute. Most of these are on GitHub so:
meltano/meltano pipeline.We qualify taps with the capabilities it supports:
--properties format for the catalog--catalog format for the catalogYou should look at the tap’s documentation to see which one is supported.
Try to run the tap with the --discover switch, which should output a catalog on STDOUT.
STATE messages.target-postgres, then validate that:
This might be a configuration issue with the catalog file that is sent to the tap. Take a look at the tap’s documentation and look for custom metadata on the catalog.