From 3b5db5cca2f31756b61b49d3cdf579b8592f13f9 Mon Sep 17 00:00:00 2001
From: Doug Beatty <44704949+dbeatty10@users.noreply.github.com>
Date: Thu, 14 Dec 2023 12:32:05 -0700
Subject: [PATCH] `merge` is the default `incremental_strategy` since
 dbt-databricks 1.0.0 (#4653)

### Previews

- [Incremental
strategies](https://docs-getdbt-com-git-dbeatty-dbt-databricks-merg-0a4e67-dbt-labs.vercel.app/reference/resource-configs/databricks-configs#incremental-models)
- [`merge`
strategy](https://docs-getdbt-com-git-dbeatty-dbt-databricks-merg-0a4e67-dbt-labs.vercel.app//reference/resource-configs/databricks-configs#the-merge-strategy)
- [`append`
strategy](https://docs-getdbt-com-git-dbeatty-dbt-databricks-merg-0a4e67-dbt-labs.vercel.app/reference/resource-configs/databricks-configs#the-append-strategy)

## What are you changing in this pull request and why?

`merge` has been the default incremental strategy for dbt-databricks
since
[1.0.0](https://github.com/databricks/dbt-databricks/blob/7ad5507a8a38bde682bb28eb37466bbfc341ac94/CHANGELOG.md?plain=1#L404)

## Checklist
- [x] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
so my content adheres to these guidelines.

---------

Co-authored-by: Matt Shaver <60105315+matthewshaver@users.noreply.github.com>
---
 .../docs/reference/resource-configs/databricks-configs.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/docs/reference/resource-configs/databricks-configs.md b/website/docs/reference/resource-configs/databricks-configs.md
index fb3c9e7f5c3..677cad57ce6 100644
--- a/website/docs/reference/resource-configs/databricks-configs.md
+++ b/website/docs/reference/resource-configs/databricks-configs.md
@@ -38,9 +38,9 @@ When materializing a model as `table`, you may include several optional configs
 ## Incremental models
 
 dbt-databricks plugin leans heavily on the [`incremental_strategy` config](/docs/build/incremental-models#about-incremental_strategy). This config tells the incremental materialization how to build models in runs beyond their first. It can be set to one of four values:
- - **`append`** (default): Insert new records without updating or overwriting any existing data.
+ - **`append`**: Insert new records without updating or overwriting any existing data.
  - **`insert_overwrite`**: If `partition_by` is specified, overwrite partitions in the <Term id="table" /> with new data. If no `partition_by` is specified, overwrite the entire table with new data.
- - **`merge`** (Delta and Hudi file format only): Match records based on a `unique_key`, updating old records, and inserting new ones. (If no `unique_key` is specified, all new data is inserted, similar to `append`.)
+ - **`merge`** (default; Delta and Hudi file format only): Match records based on a `unique_key`, updating old records, and inserting new ones. (If no `unique_key` is specified, all new data is inserted, similar to `append`.)
  - **`replace_where`** (Delta file format only): Match records based on `incremental_predicates`, replacing all records that match the predicates from the existing table with records matching the predicates from the new data. (If no `incremental_predicates` are specified, all new data is inserted, similar to `append`.)
  
 Each of these strategies has its pros and cons, which we'll discuss below. As with any model config, `incremental_strategy` may be specified in `dbt_project.yml` or within a model file's `config()` block.
@@ -49,8 +49,6 @@ Each of these strategies has its pros and cons, which we'll discuss below. As wi
 
 Following the `append` strategy, dbt will perform an `insert into` statement with all new data. The appeal of this strategy is that it is straightforward and functional across all platforms, file types, connection methods, and Apache Spark versions. However, this strategy _cannot_ update, overwrite, or delete existing data, so it is likely to insert duplicate records for many data sources.
 
-Specifying `append` as the incremental strategy is optional, since it's the default strategy used when none is specified.
-
 <Tabs
   defaultValue="source"
   values={[
@@ -195,6 +193,8 @@ The `merge` incremental strategy requires:
 
 dbt will run an [atomic `merge` statement](https://docs.databricks.com/spark/latest/spark-sql/language-manual/merge-into.html) which looks nearly identical to the default merge behavior on Snowflake and BigQuery. If a `unique_key` is specified (recommended), dbt will update old records with values from new records that match on the key column. If a `unique_key` is not specified, dbt will forgo match criteria and simply insert all new records (similar to `append` strategy).
 
+Specifying `merge` as the incremental strategy is optional since it's the default strategy used when none is specified.
+
 <Tabs
   defaultValue="source"
   values={[