-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow users to opt-out dbtRunner
during DAG parsing
#1495
Conversation
dbtRunner
during DAG parsing
✅ Deploy Preview for sunny-pastelito-5ecb04 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Deploying astronomer-cosmos with Cloudflare Pages
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1495 +/- ##
=======================================
Coverage 97.05% 97.05%
=======================================
Files 77 77
Lines 4483 4484 +1
=======================================
+ Hits 4351 4352 +1
Misses 132 132 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
I guess would be nice to highlight in our documentation somewhere that starting Cosmos 1.9, we're optimising to use dbtRunner by default for parsing and also show them how they can change the default with the corresponding param in their DAG. WDYT?
Thanks for the feedback, @pankajastro & @pankajkoti ! I've added a breaking change notice in the changelog: 14b0a2c As well as docs in 53429d9 |
While speaking to a customer about #1484, they mentioned they have the following setup:
dbt-databricks
installed in the same Python virtualenv as Cosmos/Airflowdbt-bigquery
installed in a separate Python virtualenv using Astro DockerfileAnd run DAGs using both with the same image. This means 1.9.0a3 breaks them since they use
LoadMode.DBT_LS
and onlydebt-data bricks
can be parsed. This means that we have to add support to allow users to opt-in / out of using thedbtRunner
during DAG parsing - similar to what was done for task execution, inExecutionConfig
.