首页 > 解决方案 > 为什么我得到一个“列关系的在 dbt 中运行模型但在 SQL 客户端中运行时不存在”错误?

问题描述

问题

我们有一个增量模型,已经在我们的夜间生产工作中运行了几个月(下面的 SQL)。上周,在将我们的生产环境升级到v0.21.0(从v0.19.0)之后,模型开始抛出这个错误:

Database Error in model my_model (path/to/my_model.sql)
  column "alias6" of relation "my_model" does not exist
  compiled SQL at target/run/path/to/my_model.sql
{{-
  config(
    materialized = 'incremental',
    dist = 'alias3',
    sort = 'dates_pk',
    unique_key = '__surrogate_key',
    )
-}}

with calculate_metrics as (

    select        
        field1 as dates_pk,
        field2 as alias2,
        {{ my_macro('field3') }} as alias3,
        field4 as alias4,
        field5,
        field6 as alias6,
        field7 as alias7,
        field8 as alias8,
        field9 as alias9,
        (field8::float / field6)::decimal(18, 6) as alias10,
        (field9::float / field7)::decimal(18, 6) as alias11,
        {{ dbt_utils.surrogate_key([
            'field1', 'field2', 'alias4', 'field5']) }} as __surrogate_key
    from {{ ref('upstream_model') }}
    {% if is_incremental() -%}
    where dates_pk >= coalesce((select max(dates_pk) from {{ this }}), '2000-01-01')
    {%- endif -%}

)

select * from calculate_metrics

到目前为止我尝试过的

{{-
  config(
    materialized = 'table',
    )
-}}

with calculate_metrics as (

    select        
        field1,
        field2,
        {{ my_macro('field3') }} as alias3,
        field4,
        field5,
        field6,
        field7,
        field8,
        field9
    from {{ ref('upstream_model') }}

)

select * from calculate_metrics

Database Error in model my_model (path/to/my_model.sql)
  column "dates_pk" of relation "my_model" does not exist
  compiled SQL at target/run/path/to/my_model.sql

所以dbt似乎正在运行一些数据库操作,该操作正在寻找模型中以前存在但现在不存在的别名。不知道为什么会这样,具体table化。

标签: amazon-redshiftdbt

解决方案


感谢 dbt 支持团队的一些调查,我们发现了这个问题的原因。

模型的 YML 文档文件包含模型中未找到的列名(请参阅下面的示例 YML),并且最近为模型启用了dbt 的persist_docs功能。

models:
  - name: my_model
    columns:
      ...
      # This should have been named alias6, but was not updated 
      # when the model changed at some point in the past; this
      # didn't cause an error until persist_docs attempted to
      # `comment` on the (non-existent) field in Redshift
      - name: field6
        description: Foo bar baz.

更具体的错误消息将有助于更快地解决这个问题,所以我在 dbt-core Github 上记录了这个问题。


推荐阅读