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
Right now the error message for errors related to having contracts enabled does not mention that the error is being hit because contracts are enabled for the model. Add some verbiage to the effect that the model is contracted so all the following have more context.
{%- do exceptions.raise_compiler_error('Please ensure the name, data_type, order, and number of columns in your `yml` file match the columns in your SQL file.\nSchema File Columns: ' ~ (schema_file_provided_columns_formatted|trim) ~ '\n\nSQL File Columns: ' ~ (sql_file_provided_columns_formatted|trim) ~ '' ) %}
16:00:13 Compilation Error in model my_model (models/contracted_models/my_model.sql)
16:00:13 Please ensure the name, data_type, order, and number of columns in your `yml` file match the columns in your SQL file.
16:00:13 Schema File Columns:
16:00:13
16:00:13 SQL File Columns: id INT, color TEXT, date_day DATE
16:00:13
16:00:13 > in macro assert_columns_equivalent (macros/materializations/models/table/columns_spec_ddl.sql)
16:00:13 > called by macro default__get_assert_columns_equivalent (macros/materializations/models/table/columns_spec_ddl.sql)
16:00:13 > called by macro get_assert_columns_equivalent (macros/materializations/models/table/columns_spec_ddl.sql)
16:00:13 > called by macro default__create_view_as (macros/materializations/models/view/create_view_as.sql)
16:00:13 > called by macro create_view_as (macros/materializations/models/view/create_view_as.sql)
16:00:13 > called by macro default__get_create_view_as_sql (macros/materializations/models/view/create_view_as.sql)
16:00:13 > called by macro get_create_view_as_sql (macros/materializations/models/view/create_view_as.sql)
16:00:13 > called by macro statement (macros/etc/statement.sql)
16:00:13 > called by macro materialization_view_default (macros/materializations/models/view/view.sql)
16:00:13 > called by model my_model (models/contracted_models/my_model.sql)
16:00:13
16:00:13 Done. PASS=0 WARN=0 ERROR=2 SKIP=1 TOTAL=3
The text was updated successfully, but these errors were encountered:
Right now the error message for errors related to having contracts enabled does not mention that the error is being hit because contracts are enabled for the model. Add some verbiage to the effect that the model is contracted so all the following have more context.
dbt-core/core/dbt/include/global_project/macros/materializations/models/table/columns_spec_ddl.sql
Line 44 in c02ddf8
The text was updated successfully, but these errors were encountered: