Custom S3 Path for Incremental DBT Model in Trino

[edge7]

Expected behavior

The S3 path has a meaningful name and it does not look like a temporary table

Actual behavior

The S3 path for table is something like:

all_adf_dim_account__dbt_tmp-a1df170600ea4f4eaca19dde84494979/

Steps To Reproduce

Run a dbt model with a configuration which is like:

{{ config(
    materialized= "incremental",
    unique_key="platform_account_key",
    incremental_strategy= "merge",
    tags="adf",
    labels={ "platform": "adform" },
    pre_hook= ["{{ log_countpre_rows() }}"],
    post_hook= ["{{ log_countpost_rows() }}"],
) }}

The generated table has a "weird" path that seems to be more for a temporary table.

Log output/Screenshots

No response

Operating System

NA

dbt version

1.8.0

Trino Server version

Starburst Enterprise - Trino 423

Python version

3.9

Are you willing to submit PR?

• Yes I am willing to submit a PR!