This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
v0.2.4
0.2.4
Released on October 26th, 2022.
This release introduces the ability to selectively retry failed steps in a dbt Cloud job run. dbt Cloud jobs triggered by Prefect can now be more resilient to the transient failures such as:
- Connection timeouts with a database
- Another dbt job is interacting with the same table as the current job and causing concurrency issues at the database level
Huge thanks to @dpguthrie and @sungchun12 for their help developing this new functionality!
Added
retry_dbt_cloud_job_run_subset_and_wait_for_completion
flow andretry_*
keywords intrigger_dbt_cloud_job_run_and_wait_for_completion
flow - #89get_dbt_cloud_job_info
task #89
Changed
- Allow registering all blocks at top level - #79