You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently scoping out Dagster for my team. I know Dagster makes the most sense when integrated with dbt-core and that the dbt-core integration has more features, is non-experimental, and has more flexibility. However, my organization just signed up for enterprise this year and has been enjoying CICD/dbt Explore and other quality of life features. In addition, many of our users use the dbt Cloud IDE which is why I'm limited to the dbt Cloud integration.
Having said that, I've been able to get started with and have used load_assets_from_dbt_cloud_job to connect our dbt Cloud assets to other parts of our stack and am able to materialize through Dagster. However, there are two big things that are not present in the integration with dbt Cloud:
Tests are not recognized as asset checks
They are asset observations and the results of the tests are only logged as event metadata
Therefore, there is no real observability of the test results in the UI
Model metadata is not surfaced at all to Dagster:
None of the following is available in the UI:
Raw model SQL
Model/column descriptions
dbt Tags
Compute kinds + storage details
Seeds
Because of this, it looks like Dagster may not work for us and our constraints. Is there a future feature roadmap that can implement the addition of these important asset_checks / metadata in the dbt Cloud integration?
Are there any workarounds here? or is the only way forward currently to migrate off dbt Cloud to dbt Core?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello!
I'm currently scoping out Dagster for my team. I know Dagster makes the most sense when integrated with dbt-core and that the dbt-core integration has more features, is non-experimental, and has more flexibility. However, my organization just signed up for enterprise this year and has been enjoying CICD/dbt Explore and other quality of life features. In addition, many of our users use the dbt Cloud IDE which is why I'm limited to the dbt Cloud integration.
Having said that, I've been able to get started with and have used
load_assets_from_dbt_cloud_job
to connect our dbt Cloud assets to other parts of our stack and am able to materialize through Dagster. However, there are two big things that are not present in the integration with dbt Cloud:Because of this, it looks like Dagster may not work for us and our constraints. Is there a future feature roadmap that can implement the addition of these important asset_checks / metadata in the dbt Cloud integration?
Are there any workarounds here? or is the only way forward currently to migrate off dbt Cloud to dbt Core?
Beta Was this translation helpful? Give feedback.
All reactions