important-island-738407/23/2019, 7:08 PM
. When I run into an error during the transformation I'm still getting back a success exit status from Meltano.
fierce-honey-588007/25/2019, 12:12 PM
runs. That means that, as long as the Tap|Target pipeline successfully completes and dbt runs, we always complete successfully even when dbt returns 1 (at least one handled error by dbt - i.e. some models may have been skipped) or 2 (unhandled error - eg. ctrl-c, network interruption, etc)
not running the transforms by default for a couple versions now, that means that dbt only runs intentionally. So, I think that we should update how we treat dbt exiting with an error code, return an error exit code and report back to the user that the ELT was unsuccessful. The dbt transforms are a core part of the pipeline and if they fail, something will be missing or will not be properly updated in the
schema. So this seems like something we should communicate to whoever is calling
(either the user, a script or airflow) and not exit with 0 (success) What do you think @echoing-needle-59281?
echoing-needle-5928107/25/2019, 2:33 PM
fierce-honey-588007/25/2019, 2:34 PM
echoing-needle-5928107/25/2019, 2:36 PM
important-island-738407/25/2019, 3:31 PM
when using dbt as well.