starburstdata/dbt-trino

Double `describe table`

Fokko opened this issue · 0 comments

Fokko commented

Expected behavior

We're seeing that dbt-trino is quite chatty (this is more a charasteristic of dbt, rather than dbt-trino). I noticed that when running an incremental model, we're seeing a double describe table:

�[0m23:26:43.242406 [debug] [Thread-1  ]: SQL status: SUCCESS in 0.0 seconds
�[0m23:26:43.247471 [debug] [Thread-1  ]: Using trino connection "model.dbt_tabular.locations_incremental"
�[0m23:26:43.247764 [debug] [Thread-1  ]: On model.dbt_tabular.locations_incremental: /* {"app": "dbt", "dbt_version": "1.5.2", "profile_name": "default", "target_name": "dev", "node_id": "model.dbt_tabular.locations_incremental"} */
describe                sandbox.dbt_trino.locations_incremental
�[0m23:26:43.646770 [debug] [Thread-1  ]: SQL status: SUCCESS in 0.0 seconds
�[0m23:26:43.654199 [debug] [Thread-1  ]: Using trino connection "model.dbt_tabular.locations_incremental"
�[0m23:26:43.654482 [debug] [Thread-1  ]: On model.dbt_tabular.locations_incremental: /* {"app": "dbt", "dbt_version": "1.5.2", "profile_name": "default", "target_name": "dev", "node_id": "model.dbt_tabular.locations_incremental"} */
describe                "sandbox"."dbt_trino"."locations_incremental"

Actual behavior

I would expect one describe table

Steps To Reproduce

This can be observed when running a incremental model:

{{ config(
  persist_docs={"relation": true, "columns": true},
  file_format="iceberg",
  materialized="incremental",
  unique_key='location_id',
  incremental_strategy='delete+insert',
) }}

SELECT *
FROM examples.nyc_taxi_locations

Log output/Screenshots

No response

Operating System

OSX

dbt version

1.5.0

Trino Server version

419

Python version

Python 3.9.6

Are you willing to submit PR?

  • Yes I am willing to submit a PR!