-
Notifications
You must be signed in to change notification settings - Fork 182
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
No datasets emitted in DbtLocalBaseOperator after Cosmos upgrade to 1.3.0 #796
Comments
🤖 That sounds like a great proposal! It's clear that you've put thought into the issue and have a solid plan for addressing it. Encouraging user contributions is a fantastic way to improve Cosmos for everyone, and your proposed solution seems like a step in the right direction. I encourage you to go ahead and create a pull request with your proposed changes. Your contribution will be valuable to the Cosmos community. Keep up the great work! This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot. |
@jakob-hvitnov-telia do things work as expected if you install |
@tatiana installing apache-airflow-providers-openlineage did the trick! So in the end it seems the Airflow update was more the culprit than the Cosmos update. Thank you very much for your help! |
Remove incorrect docstring from `DbtLocalBaseOperator` (relatest to #796) --------- Co-authored-by: Justin Bandoro <[email protected]> Co-authored-by: Tatiana Al-Chueyr <[email protected]>
[Cosmos docs](https://astronomer.github.io/astronomer-cosmos/configuration/lineage.html) stated that users didn't have to install any dependency to use OpenLineage with Cosmos. However, for inlets and outlets to be emitted, Airflow 2.7 users must install `apache-airflow-providers-openlineage` or `astronomer-cosmos[openlineage]`. Closes: #796
Remove incorrect docstring from `DbtLocalBaseOperator` (relatest to #796) --------- Co-authored-by: Justin Bandoro <[email protected]> Co-authored-by: Tatiana Al-Chueyr <[email protected]> (cherry picked from commit ef2c7bb)
[Cosmos docs](https://astronomer.github.io/astronomer-cosmos/configuration/lineage.html) stated that users didn't have to install any dependency to use OpenLineage with Cosmos. However, for inlets and outlets to be emitted, Airflow 2.7 users must install `apache-airflow-providers-openlineage` or `astronomer-cosmos[openlineage]`. Closes: #796 (cherry picked from commit fe01237)
Remove incorrect docstring from `DbtLocalBaseOperator` (relatest to astronomer#796) --------- Co-authored-by: Justin Bandoro <[email protected]> Co-authored-by: Tatiana Al-Chueyr <[email protected]>
[Cosmos docs](https://astronomer.github.io/astronomer-cosmos/configuration/lineage.html) stated that users didn't have to install any dependency to use OpenLineage with Cosmos. However, for inlets and outlets to be emitted, Airflow 2.7 users must install `apache-airflow-providers-openlineage` or `astronomer-cosmos[openlineage]`. Closes: astronomer#796
After updating Cosmos from 1.1.3 to 1.3.0 we have run into an issue where we are no longer seeing emission of datasets when using theDbtRunLocal operator.
At the same update we went from Airflow 2.6.3 to 2.7.2.
Dag log output (from dbt_run task) before the update:
Dag log output after the update:
We are running on AWS MWAA.
I suspect the change in has something to do with this commit as this introduces the get_datasets method, which in its docstring clarifies that the method relies on:
It is not quite clear to me if these are generated by our call to DbtRunLocal at the moment.
There might be configuration options I am overlooking:
Docstring typo
Also in DbtLocalBaseOperator there seems to be an error in the docstring (lines 97-98) where it says:
I think the phrasing should probably be:
A fix for this is in https://github.com/astronomer/astronomer-cosmos/pull/797
The text was updated successfully, but these errors were encountered: