diff --git a/integrations/connect-project.mdx b/integrations/connect-project.mdx index 8ec9ab14e..21053b33f 100644 --- a/integrations/connect-project.mdx +++ b/integrations/connect-project.mdx @@ -33,9 +33,9 @@ Changing the warehouse connection doesn't change the tables in Explore. They sti ## 1. Connect to a warehouse -We currently support [BigQuery](#bigquery), [Postgres](#postgres), [Supabase](#supabase), [Redshift](#redshift), [Snowflake](#snowflake), [Databricks](#databricks), [Trino](#trino), [ClickHouse](#clickhouse), [DuckDB](#duckdb), and [Athena](#athena). If your warehouse isn't listed, you may still be able to connect to it through [Trino](#trino). +Lightdash supports [BigQuery](#bigquery), [Postgres](#postgres), [Supabase](#supabase), [Redshift](#redshift), [Snowflake](#snowflake), [Databricks](#databricks), [Trino](#trino), [ClickHouse](#clickhouse), [DuckDB](#duckdb) and [Athena](#athena). If your warehouse isn't listed, you may still be able to connect to it through [Trino](#trino). -We always recommend giving read-only permissions to Lightdash, that way you ensure than no data can be manipulated. See each section below for warehouse specific details. +Give Lightdash read-only permissions so it can't change your data. A Postgres, Athena or Snowflake project can also query more than one warehouse. See [multiple warehouse connections](/workspace-admin/multiple-warehouse-connections). @@ -1504,9 +1504,9 @@ Then scroll down to the dbt project section: The dbt connection section of Lightdash project settings, with type GitHub, OAuth authorization, and repository, dbt version, and branch fields -The **dbt version** field sets the dbt Core 1.x version Lightdash uses when it compiles your project. Lightdash supports dbt Core 1.4 to 1.12. The default, **latest**, uses the newest version Lightdash supports, currently 1.12. If a refresh fails with a dbt compile error and the project is pinned to an older version, choose a newer version, or **latest**, and refresh again. `lightdash deploy` and `lightdash preview` compile with the dbt you have installed, so for those, upgrade dbt locally. The list has no dbt Core v2 (Fusion) option: for a Fusion project, keep **latest** and keep the project compatible with dbt Core 1.10 or later, as described in [Moving to dbt Core v2 (Fusion)](/integrations/dbt/upgrading#moving-to-dbt-core-v2-fusion). +The **dbt version** field sets the dbt Core 1.x version Lightdash uses when it compiles your project. Lightdash supports dbt Core 1.4 to 1.12. The default, **latest**, uses the newest version Lightdash supports, currently 1.12. If a refresh fails with a dbt compile error and the project is pinned to an older version, choose a newer version, or **latest**, and refresh again. `lightdash deploy` and `lightdash preview` compile with the dbt you have installed, so for those, upgrade dbt locally. The list has no dbt v2 option: for a dbt v2 project, keep **latest** and keep the project compatible with dbt Core 1.10 or later, as described in [Moving to dbt v2](/integrations/dbt/upgrading#moving-to-dbt-v2-fusion). -Pick your connection type and follow the guide below: [GitHub](#github), [GitLab](#gitlab), [Azure DevOps](#azure-devops), [Bitbucket](#bitbucket), [dbt Cloud](#dbt-cloud), or the [CLI](#cli). +Pick your connection type and follow its section below: [GitHub](#github), [GitLab](#gitlab), [Azure DevOps](#azure-devops), [Bitbucket](#bitbucket), [dbt Cloud](#dbt-cloud), or the [CLI](#cli). **dbt Cloud managed repositories** diff --git a/integrations/dbt/upgrading.mdx b/integrations/dbt/upgrading.mdx index 067aa45ca..8e975a9ff 100644 --- a/integrations/dbt/upgrading.mdx +++ b/integrations/dbt/upgrading.mdx @@ -3,7 +3,17 @@ title: "Upgrading dbt" description: "What changes in your Lightdash setup when you move between dbt versions" --- -Lightdash reads your dbt project, so a dbt upgrade can change how your semantic layer is declared. Two changes matter: where `meta` and `tags` live as of 1.10, and the Fusion engine that ships as dbt Core v2. +Lightdash reads your dbt project, so a dbt upgrade can change how your semantic layer is declared. Two changes matter: where `meta` and `tags` live as of 1.10, and the move to dbt v2 (formerly Fusion). + +## dbt versions + +dbt comes in three forms, and Lightdash compiles each one differently. + +| Release | What it is | How Lightdash compiles it | +| --- | --- | --- | +| **dbt Core 1.x** | The Python releases. From 1.10, `meta` and `tags` move under `config:`, as described below. | Git connection refreshes use the [**dbt version**](/integrations/connect-project#2-import-a-dbt-project) set for the project. The CLI uses the version you have installed. | +| **dbt v2** | The Rust rewrite formerly called Fusion, under the dbt Product License. | CLI only. Git-connected projects have no v2 option. | +| **dbt OSS v2** | The Apache 2.0 build of the Rust rewrite. Some features differ from dbt v2 at the same version. `dbt --version` prints `dbt-oss`. | CLI only, from Lightdash CLI 3.209.1. | ## Moving to dbt 1.10 @@ -308,11 +318,13 @@ For projects with hundreds of YAML files: 2. Use the `-o` flag to organize transformed files by directory 3. Process files in batches to make review manageable -## Moving to dbt Core v2 (Fusion) + + +## Moving to dbt v2 (Fusion) -The Fusion engine is a rewrite of dbt in Rust, with faster builds, native SQL understanding, and real-time validation. It is not a separate product: **Fusion ships as dbt Core v2**, and it is open source like the Core releases before it. The proprietary parts of dbt live in dbt Cloud, which you reach by logging in from the CLI — the engine itself is not gated. +dbt v2, the Rust rewrite formerly called Fusion, has faster builds, native SQL understanding, and real-time validation. It ships as dbt v2 and dbt OSS v2; see [dbt versions](#dbt-versions). -Your SQL and YAML syntax is unchanged. What differs is enforcement: Fusion validates more strictly than earlier Core releases, so a project carrying unresolved deprecation warnings will fail on it. +Your SQL and YAML syntax is unchanged. What differs is enforcement: dbt v2 validates more strictly than dbt Core 1.x, so a project carrying unresolved deprecation warnings will fail on it. ### Before you upgrade @@ -323,5 +335,5 @@ Your SQL and YAML syntax is unchanged. What differs is enforcement: Fusion valid Check the [dbt Fusion documentation](https://docs.getdbt.com/docs/fusion/about-fusion) for engine-specific behavior and any features still landing. - The Lightdash CLI works with Fusion: `lightdash deploy` and `lightdash preview` compile your project with the dbt you have installed, including Fusion. When Lightdash compiles your project itself, on a [Git connection refresh](/integrations/dbt/projects#git-connection-methods), it uses dbt Core 1.x at the dbt version set in your [project connection settings](/integrations/connect-project#2-import-a-dbt-project). Keep your project compatible with dbt Core 1.10 or later so both paths compile it. + Git connection refreshes compile with dbt Core 1.x, while the CLI uses the dbt v2 you have installed. Keep your project compatible with dbt Core 1.10 or later so both compile it.