-
Notifications
You must be signed in to change notification settings - Fork 177
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
Analysis ResourceType #579
Comments
Hello @nicohein , I've seen similar errors thrown in tandem with a DagBag timeout error. Can you increase the DagBag import time |
@erdos2n yes, I increased the timeout to 300s, after seeing a DagBag timeout before. This error is independent. The Dag refill times for cosmos DAGs are really long though and varying a lot by Loadmode. DBT_LS with dbt_deps flag is by far the slowest on the setup I have. @tatiana The issue is that as soon as there is an analysis node in the manifest, astronomer-cosmos is unable to parse the manifest. It can ignore and should ignore those nodes but it should still be able to parse the manifest and not throw an error. Changing the ValueError to a warning would equally work here and would probably be more future proof. |
Hi @nicohein, we just released Cosmos 1.2:
Could you confirm if the issue is still happening with the new version? |
Hi @tatiana , Initially, I got the below error:
I can work around this problem by passing the dbt_project_path as a Path.
After this, I could then test for the |
When testing astronomer-cosmos with the manifest json parse method I am receiving the following error
However, according to the dbt documentation analysis is a valid resource type: https://docs.getdbt.com/reference/commands/list
I am not sure about the impact but would hope a simple addition to this Enum would solve the problem:
astronomer-cosmos/cosmos/constants.py
Line 53 in 2e3e4fd
dbt version 1.5.7
astronomer-cosmos version 1.1.3
The text was updated successfully, but these errors were encountered: