skw
10/05/2020, 9:28 PMPL/Python in a dbt transformation, but its not an official PostgreSQL plugin, not supported by AWS RDS, and likely neither functional nor practical within dbt .
Currently, it runs regularly via a CRON job. The most straightforward solution is to call it via an Airflow operator
That said, I don’t see best practices documented at Meltano regarding this type of setup. Does anyone here have a similar setup? How do you think about running crucial transformations that don’t neatly fall into the `tap`/ `target`/`dbt` categories in the context of Meltano?skw
10/05/2020, 9:35 PMpapermill . I know that development is not there yet, but if anyone can point me to best practices or a high-level framework for making design decisions, it’d be a huge help.
Thanks!douwe_maan
10/05/2020, 9:35 PMmeltano elt just be a step in your manually crafted Airflow DAG, followed by whatever additional steps you'd like. This is the approach also commonly taken by people who already have Airflow and dbt set up, and just want to bring in Meltano for the EL step.skw
10/05/2020, 9:46 PM