Skip to content

Commit

Permalink
Add on_table_exists 'replace' option to Starburst/Trino
Browse files Browse the repository at this point in the history
  • Loading branch information
damian3031 committed Dec 21, 2023
1 parent d472df5 commit 1dad0f0
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion website/docs/reference/resource-configs/trino-configs.md
Original file line number Diff line number Diff line change
Expand Up @@ -97,8 +97,9 @@ The `dbt-trino` adapter supports these modes in `table` materialization, which y

- `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.
- `replace` — Replaces a table using CREATE OR REPLACE clause. Support for table replacement varies across connectors. Refer to the connector documentation for details.

The recommended `table` materialization uses `on_table_exists = 'rename'` and is also the default. You can change this default configuration by editing _one_ of these files:
If CREATE OR REPLACE is supported in underlying connector, `replace` is recommended option. Otherwise, the recommended `table` materialization uses `on_table_exists = 'rename'` and is also the default. You can change this default configuration by editing _one_ of these files:
- the SQL file for your model
- the `dbt_project.yml` configuration file

Expand Down

0 comments on commit 1dad0f0

Please sign in to comment.