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've tried to use SQLMesh on a dbt project but got the following error when launching the UI:
It'd be great if the error logs would specify the exact models that are causing the circular references the same way dbt does, for example: RuntimeError: Found a cycle: model.dbt_cyclical_project.model_a --> model.dbt_cyclical_project.model_b
I didn't get the circular references error when running the same models with dbt instead of SQLMesh, so it'd be great for me to understand what models are causing an error in SQLMesh but not in dbt
The text was updated successfully, but these errors were encountered:
@zoltanmihaly most likely one of the models has a dbt test (audit in SQLMesh terms) which references a model downstream.
Unlike dbt, SQLMesh audits are part of the model evaluation and not a separate step. That's why a cyclic reference in an audit leads to a failure in SQLMesh but not dbt.
I've tried to use SQLMesh on a dbt project but got the following error when launching the UI:
It'd be great if the error logs would specify the exact models that are causing the circular references the same way dbt does, for example:
RuntimeError: Found a cycle: model.dbt_cyclical_project.model_a --> model.dbt_cyclical_project.model_b
I didn't get the circular references error when running the same models with dbt instead of SQLMesh, so it'd be great for me to understand what models are causing an error in SQLMesh but not in dbt
The text was updated successfully, but these errors were encountered: