Merge branch 'current' into teradata-setup-changes

website/docs/docs/build/incremental-models.md

@@ -212,11 +212,11 @@ Currently, `on_schema_change` only tracks top-level column changes. It does not
 
 ### Default behavior
 
-This is the behavior if `on_schema_change: ignore`, which is set by default, and on older versions of dbt.
+This is the behavior of `on_schema_change: ignore`, which is set by default.
 
 If you add a column to your incremental model, and execute a `dbt run`, this column will _not_ appear in your target table.
 
-Similarly, if you remove a column from your incremental model, and execute a `dbt run`, this column will _not_ be removed from your target table.
+If you remove a column from your incremental model and execute a `dbt run`, `dbt run` will fail.
 
 Instead, whenever the logic of your incremental changes, execute a full-refresh run of both your incremental model and any downstream models.
 

website/docs/reference/global-configs/cache.md

@@ -6,7 +6,7 @@ sidebar: "Cache"
 
 ### Cache population
 
-At the start of runs, dbt caches metadata about all the objects in all the schemas where it might materialize resources (such as models). By default, dbt populates the cache with information on all schemas related to the project.
+At the start of runs, dbt caches metadata about all the objects in all the schemas where it might materialize resources (such as models). By default, dbt populates the relational cache with information on all schemas related to the project.
 
 There are two ways to optionally modify this behavior:
 - `POPULATE_CACHE` (default: `True`): Whether to populate the cache at all. To skip cache population entirely, use the `--no-populate-cache` flag or `DBT_POPULATE_CACHE: False`. Note that this does not _disable_ the cache; missed cache lookups will run queries, and update the cache afterward.
@@ -26,3 +26,11 @@ Or, to improve speed and performance while focused on developing Salesforce mode
 dbt --cache-selected-only run --select salesforce
 
 ```
+
+### Logging relational cache events
+
+import LogLevel from '/snippets/_log-relational-cache.md';
+
+<LogLevel
+event="relational cache"
+/>

website/docs/reference/global-configs/logs.md

@@ -137,11 +137,11 @@ You can use either of these parameters to ensure clean output that's compatible
 
 ### Logging relational cache events
 
-The `LOG_CACHE_EVENTS` config allows detailed logging for [relational cache](/reference/global-configs/cache) events, which are disabled by default.
+import LogLevel from '/snippets/_log-relational-cache.md';
 
-```text
-dbt --log-cache-events compile
-```
+<LogLevel
+event={<a href="https://docs.getdbt.com/reference/global-configs/cache">relational cache</a>}
+/>
 
 ### Color
 

website/snippets/_log-relational-cache.md

@@ -0,0 +1,5 @@
+<p>The `LOG_CACHE_EVENTS` config allows detailed logging for {props.event}, which are disabled by default.</p>
+
+```text
+dbt --log-cache-events compile
+```

website/snippets/_sl-partner-links.md

@@ -22,6 +22,20 @@ The following tools integrate with the dbt Semantic Layer:
     body="Connect to Microsoft Excel to query metrics and collaborate with your team. Available for Excel Desktop or Excel Online."
     icon="excel"/>
 
+  <div className="card-container">
+    <Card
+      title="Dot"
+      link="https://docs.getdot.ai/dot/integrations/dbt-semantic-layer"
+      body="Enable everyone to analyze data with AI in Slack or Teams."
+      icon="dot-ai"/>
+      <a href="https://docs.getdot.ai/dot/integrations/dbt-semantic-layer"
+      className="external-link"
+      target="_blank"
+      rel="noopener noreferrer">
+      <Icon name='fa-external-link' />
+    </a>
+  </div>
+
   <div className="card-container">
     <Card
       title="Hex"