Closed il-dat closed 9 months ago
The model.sql model has the columns in following order:
model.sql
cast(null as {{ type_string() }}) as command_invocation_id
cast(null as {{ type_string() }}) as node_id
But the macro (upload result) is following the reversed order:
node_id
command_invocation_id
Encountered in snowflake and dbt-artifacts v2.6.0
snowflake
dbt-artifacts
Make sure the column order is matching to the upload macros
Results of running dbt --version: 1.6 latest
dbt --version
Please paste the contents of your packages.yml file here:
packages.yml
packages: - package: dbt-labs/dbt_utils version: 1.1.1 - package: dbt-labs/codegen version: 0.10.0 - package: dbt-labs/dbt_project_evaluator version: 0.7.3 - package: infinitelambda/dq_tools version: [">=1.4.0", "<1.5.0"] - package: get-select/dbt_snowflake_monitoring version: 4.5.1 - package: brooklyn-data/dbt_artifacts version: [">=2.6.0", "<2.7.0"]
Once again thanks for raising and spotting this. I've now merged the PR and created a release with it in. Please do reach out if there is anything else you spot.
Overview
The
model.sql
model has the columns in following order:cast(null as {{ type_string() }}) as command_invocation_id
cast(null as {{ type_string() }}) as node_id
But the macro (upload result) is following the reversed order:
node_id
command_invocation_id
How to reproduce
Encountered in
snowflake
anddbt-artifacts
v2.6.0Expected behaviour
Make sure the column order is matching to the upload macros
Screenshots
Environment
Results of running
dbt --version
: 1.6 latestPlease paste the contents of your
packages.yml
file here: