Closed tallamohan closed 2 months ago
This macro is the one generating the None
database:
{% macro teradata__generate_database_name(custom_database_name=none, node=none) -%}
{% do return(None) %}
{%- endmacro %}
I've found the same logic in a few other dbt adapters, namely:
It would be great to have dagster just skip over the database key in these cases.
Yes @amaralvieira , same as dbt-teradata a few adapters do not consider database.
This is the code in dagster-dbt which is throwing the error:
dbt_resource_props["database"]
should be skipped when None to accommodate the adapters above.
I encountered a similar issue while setting up a project with dbt and MySQL. The setup works perfectly when I use PostgreSQL in the dbt profiles, but it fails consistently with MySQL. As mentioned previously, the dbt-mysql adapter is the issue I believe.
I've submitted a PR: https://github.com/dagster-io/dagster/pull/24021 Please give it a review if you know dagster's code base a bit :wink:
Dagster version
1.7.13
What's the issue?
In dbt-teradata adapter, the database value is set as None. It considers only the schema value But in the latest dagster-dbt, asset_utils.py tries to build relation_name using the "database" value in the manifest.json file.
I am trying to add a sample dbt project as an asset using this tutorial: https://docs.dagster.io/integrations/dbt/using-dbt-with-dagster/load-dbt-models
But after staring the "dagster dev" server, I am seeing this error:
What did you expect to happen?
Successfully load dbt project of dbt-teradata adapter
How to reproduce?
Load any dbt project which uses dbt-teradata adapter
Deployment type
Local
Deployment details
No response
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.