Open cbini opened 1 month ago
Some of catalogs use two component names, Spark for instance. In that case dbt_resource_props["database"]
will be present in the manifest.json but dbt_resource_props["database"] will be None
Suggest adding extra condition to validation
if (
"database" in dbt_resource_props
and "schema" in dbt_resource_props
and "alias" in dbt_resource_props
):
relation_name = ".".join(
[
dbt_resource_props["database"],
dbt_resource_props["schema"],
dbt_resource_props["alias"],
]
)
Dagster version
1.7.14
What's the issue?
When building column metadata for models that are installed from dbt dependencies, the function fails and Dagster logs a warning, presumably because the source SQL file doesn't exist on the project. I could be wrong--I would think the SQL should be present in the target folder, but Dagster isn't finding it.
What did you expect to happen?
To be clear, the run still succeeds and the asset materializes, but it would be great to find a way around this or explicitly log that these types of models aren't supported.
How to reproduce?
run using a dbt model that's installed from a dbt dependency:
Deployment type
Dagster Cloud
Deployment details
Hybrid
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.