From b3c5fb450c374786c0c30b5ff4f467a782a6162b Mon Sep 17 00:00:00 2001 From: Damian Owsianny Date: Fri, 17 May 2024 11:14:46 +0200 Subject: [PATCH] Starburst/Trino - on_table_exists modes are applicable to a full-refresh run of an incremental model --- website/docs/reference/resource-configs/trino-configs.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/website/docs/reference/resource-configs/trino-configs.md b/website/docs/reference/resource-configs/trino-configs.md index 9ee62959f76..b4aeb4dbeee 100644 --- a/website/docs/reference/resource-configs/trino-configs.md +++ b/website/docs/reference/resource-configs/trino-configs.md @@ -93,7 +93,7 @@ Another way to avoid the header line length limit is to set `prepared_statements ## Materializations ### Table -The `dbt-trino` adapter supports these modes in `table` materialization, which you can configure with `on_table_exists`: +The `dbt-trino` adapter supports these modes in `table` materialization (and [full-refresh runs](/reference/commands/run#refresh-incremental-models) in `incremental` materialization), which you can configure with `on_table_exists`: - `rename` — Creates an intermediate table, renames the target table to the backup one, and renames the intermediate table to the target one. - `drop` — Drops and re-creates a table. This overcomes the table rename limitation in AWS Glue. @@ -194,6 +194,8 @@ Use the `+on_schema_change` property to define how dbt-trino should handle colum If your connector doesn't support views, set the `+views_enabled` property to `false`. +You can decide how model should be rebuilt in a `full-refresh` run by specifying `on_table_exists` config. Options are the same as described in [table materialization section](/reference/resource-configs/trino-configs#table) + #### append strategy The default incremental strategy is `append`. `append` only adds new records based on the condition specified in the `is_incremental()` conditional block.