From d6313db1440e7e20c7930fe477dde461acd47f1c Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 10 Dec 2025 15:36:46 +0000 Subject: [PATCH 1/7] Update dbt-guides/dbt-fusion-migration.mdx Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> --- dbt-guides/dbt-fusion-migration.mdx | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/dbt-guides/dbt-fusion-migration.mdx b/dbt-guides/dbt-fusion-migration.mdx index 121a1e89..7ad639fb 100644 --- a/dbt-guides/dbt-fusion-migration.mdx +++ b/dbt-guides/dbt-fusion-migration.mdx @@ -12,6 +12,18 @@ Unlike dbt 1.10 which is an incremental update, Fusion represents a fundamental Important: dbt Fusion is still in beta, which means some dbt functionality is not supported at present. Please review the [dbt Fusion supported features and current limitations documentation](https://docs.getdbt.com/docs/fusion/supported-features) before proceeding with this migration. +### How dbt Fusion works with the Lightdash CLI + +Lightdash CLI works seamlessly with dbt Fusion because Fusion projects follow the dbt 1.10+ project structure. You can run Fusion locally, and Lightdash CLI commands will still work because Lightdash never executes your dbt code—it only reads your project files and compiles SQL. Lightdash does not run Fusion internally; it simply uses your project metadata to compile queries. + +### Why Lightdash still compiles with dbt Core v1.10+ + +Lightdash always compiles your project using dbt Core 1.10+, even if you run Fusion locally, because Lightdash only needs to parse your YAML and generate its own manifest. Fusion and 1.10+ share the same configuration pattern—specifically the updated `config.meta` syntax—so Lightdash's compiler can understand both without needing Fusion support inside the product. Since Fusion projects remain backward-compatible with dbt Core, Lightdash can reliably compile them using Core alone. + + + We'll be updating all documentation code snippets to reflect the v1.10+ YAML structure (`config.meta`) soon. + + ## Recommended Migration Process ### Step 1: Upgrade to dbt 1.10 and Fix Warnings From 7b1e335180bd461a9287f1c11c2d5ee3e19e6e87 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 10 Dec 2025 15:42:49 +0000 Subject: [PATCH 2/7] Documentation edits made through Mintlify web editor --- dbt-guides/dbt-fusion-migration.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/dbt-guides/dbt-fusion-migration.mdx b/dbt-guides/dbt-fusion-migration.mdx index 7ad639fb..a38eeb9e 100644 --- a/dbt-guides/dbt-fusion-migration.mdx +++ b/dbt-guides/dbt-fusion-migration.mdx @@ -14,11 +14,11 @@ Unlike dbt 1.10 which is an incremental update, Fusion represents a fundamental ### How dbt Fusion works with the Lightdash CLI -Lightdash CLI works seamlessly with dbt Fusion because Fusion projects follow the dbt 1.10+ project structure. You can run Fusion locally, and Lightdash CLI commands will still work because Lightdash never executes your dbt code—it only reads your project files and compiles SQL. Lightdash does not run Fusion internally; it simply uses your project metadata to compile queries. +Lightdash CLI works seamlessly with dbt Fusion because Fusion projects follow the dbt 1.10+ project structure. You can run Fusion locally, and Lightdash CLI commands will still work because Lightdash never executes your dbt code; it simply uses your project metadata to compile queries. ### Why Lightdash still compiles with dbt Core v1.10+ -Lightdash always compiles your project using dbt Core 1.10+, even if you run Fusion locally, because Lightdash only needs to parse your YAML and generate its own manifest. Fusion and 1.10+ share the same configuration pattern—specifically the updated `config.meta` syntax—so Lightdash's compiler can understand both without needing Fusion support inside the product. Since Fusion projects remain backward-compatible with dbt Core, Lightdash can reliably compile them using Core alone. +Lightdash always compiles your project using dbt Core 1.10+, even if you run Fusion locally, because Lightdash only needs to parse your YAML and generate its own manifest. Fusion and 1.10+ share the same configuration pattern - specifically the updated `config.meta` syntax - so Lightdash's compiler can understand both without needing Fusion support inside the product. Since Fusion projects remain backward-compatible with dbt Core, Lightdash can reliably compile them using Core alone. We'll be updating all documentation code snippets to reflect the v1.10+ YAML structure (`config.meta`) soon. From 67001d1fbd13f36fd3c9cfa3cd1117ecbb7b4e38 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 10 Dec 2025 15:43:38 +0000 Subject: [PATCH 3/7] Documentation edits made through Mintlify web editor --- dbt-guides/dbt-fusion-migration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dbt-guides/dbt-fusion-migration.mdx b/dbt-guides/dbt-fusion-migration.mdx index a38eeb9e..edb01885 100644 --- a/dbt-guides/dbt-fusion-migration.mdx +++ b/dbt-guides/dbt-fusion-migration.mdx @@ -21,7 +21,7 @@ Lightdash CLI works seamlessly with dbt Fusion because Fusion projects follow th Lightdash always compiles your project using dbt Core 1.10+, even if you run Fusion locally, because Lightdash only needs to parse your YAML and generate its own manifest. Fusion and 1.10+ share the same configuration pattern - specifically the updated `config.meta` syntax - so Lightdash's compiler can understand both without needing Fusion support inside the product. Since Fusion projects remain backward-compatible with dbt Core, Lightdash can reliably compile them using Core alone. - We'll be updating all documentation code snippets to reflect the v1.10+ YAML structure (`config.meta`) soon. + We'll be updating all documentation code snippets to include dbt v1.10+ YAML structure (`config.meta`) soon. ## Recommended Migration Process From eaae9788117763f0b0464a6ae08a80b165615d92 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 10 Dec 2025 18:50:26 +0000 Subject: [PATCH 4/7] Documentation edits made through Mintlify web editor --- dbt-guides/dbt-fusion-migration.mdx | 28 +++++++++++++++++++++------- 1 file changed, 21 insertions(+), 7 deletions(-) diff --git a/dbt-guides/dbt-fusion-migration.mdx b/dbt-guides/dbt-fusion-migration.mdx index edb01885..e28ebddb 100644 --- a/dbt-guides/dbt-fusion-migration.mdx +++ b/dbt-guides/dbt-fusion-migration.mdx @@ -12,17 +12,31 @@ Unlike dbt 1.10 which is an incremental update, Fusion represents a fundamental Important: dbt Fusion is still in beta, which means some dbt functionality is not supported at present. Please review the [dbt Fusion supported features and current limitations documentation](https://docs.getdbt.com/docs/fusion/supported-features) before proceeding with this migration. -### How dbt Fusion works with the Lightdash CLI + + We'll be updating all documentation code snippets to include dbt v1.10+ YAML structure (`config.meta`) soon. + -Lightdash CLI works seamlessly with dbt Fusion because Fusion projects follow the dbt 1.10+ project structure. You can run Fusion locally, and Lightdash CLI commands will still work because Lightdash never executes your dbt code; it simply uses your project metadata to compile queries. +## Using dbt Fusion with Lightdash -### Why Lightdash still compiles with dbt Core v1.10+ +dbt Fusion is compatible with Lightdash, but it behaves slightly differently depending on whether you're working **locally** or compiling your project on **Lightdash servers**. -Lightdash always compiles your project using dbt Core 1.10+, even if you run Fusion locally, because Lightdash only needs to parse your YAML and generate its own manifest. Fusion and 1.10+ share the same configuration pattern - specifically the updated `config.meta` syntax - so Lightdash's compiler can understand both without needing Fusion support inside the product. Since Fusion projects remain backward-compatible with dbt Core, Lightdash can reliably compile them using Core alone. +### Local development: dbt Fusion CLI + Lightdash CLI +You can use the dbt Fusion CLI (`dbtf`) together with the Lightdash CLI during local development. +The Lightdash CLI does **not** run dbt itself; it relies entirely on the manifest (`manifest.json`) generated by *your* dbt tool. Since dbt Fusion produces a Core-compatible manifest, Lightdash CLI commands (such as `lightdash preview` and `lightdash deploy`) work as expected. - - We'll be updating all documentation code snippets to include dbt v1.10+ YAML structure (`config.meta`) soon. - +### On Lightdash: Why your project still compiles with dbt Core 1.10+ +When you connect your dbt project to Lightdash or trigger a build in the UI, Lightdash compiles your project using **dbt Core 1.10+**, even if you're running Fusion locally. + +This works because: + +- dbt Fusion follows the **same configuration model** as dbt Core 1.10+ (including the `config.meta` structure). +- Fusion outputs a **Core-compatible manifest**, which Lightdash can parse without needing a Fusion runtime. + +### Which dbt version should I choose in the Lightdash UI? +When asked to select a dbt version, choose **dbt Core 1.10+**, even if your local workflow uses dbt Fusion. +Fusion projects are fully compatible with Lightdash’s Core-based compilation as long as the project conforms to the dbt 1.10+ structure. + +--- ## Recommended Migration Process ### Step 1: Upgrade to dbt 1.10 and Fix Warnings From 63e25049b5f02384051638fddb2be5dbed7ba70c Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 10 Dec 2025 18:51:00 +0000 Subject: [PATCH 5/7] Documentation edits made through Mintlify web editor --- dbt-guides/dbt-fusion-migration.mdx | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/dbt-guides/dbt-fusion-migration.mdx b/dbt-guides/dbt-fusion-migration.mdx index e28ebddb..36e1694b 100644 --- a/dbt-guides/dbt-fusion-migration.mdx +++ b/dbt-guides/dbt-fusion-migration.mdx @@ -12,10 +12,6 @@ Unlike dbt 1.10 which is an incremental update, Fusion represents a fundamental Important: dbt Fusion is still in beta, which means some dbt functionality is not supported at present. Please review the [dbt Fusion supported features and current limitations documentation](https://docs.getdbt.com/docs/fusion/supported-features) before proceeding with this migration. - - We'll be updating all documentation code snippets to include dbt v1.10+ YAML structure (`config.meta`) soon. - - ## Using dbt Fusion with Lightdash dbt Fusion is compatible with Lightdash, but it behaves slightly differently depending on whether you're working **locally** or compiling your project on **Lightdash servers**. @@ -53,4 +49,6 @@ Once all deprecation warnings are resolved, dbt Core users will need to follow t 2. Install the dbt Fusion engine following the [installation guide](https://docs.getdbt.com/docs/fusion/install-fusion#install-fusion) 3. Run your project with dbt Fusion to identify any compatibility issues. - + + We'll be updating all documentation code snippets to include dbt v1.10+ YAML structure (`config.meta`) soon. + \ No newline at end of file From 107daf864218678d4eafe94a267d3f603889c572 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 10 Dec 2025 18:59:38 +0000 Subject: [PATCH 6/7] Documentation edits made through Mintlify web editor --- dbt-guides/dbt-fusion-migration.mdx | 22 +++++----------------- 1 file changed, 5 insertions(+), 17 deletions(-) diff --git a/dbt-guides/dbt-fusion-migration.mdx b/dbt-guides/dbt-fusion-migration.mdx index 36e1694b..a96bb80e 100644 --- a/dbt-guides/dbt-fusion-migration.mdx +++ b/dbt-guides/dbt-fusion-migration.mdx @@ -14,25 +14,13 @@ Unlike dbt 1.10 which is an incremental update, Fusion represents a fundamental ## Using dbt Fusion with Lightdash -dbt Fusion is compatible with Lightdash, but it behaves slightly differently depending on whether you're working **locally** or compiling your project on **Lightdash servers**. +dbt Fusion is compatible with Lightdash for both local development and cloud-based compilation, but a few behaviors differ from dbt Core. -### Local development: dbt Fusion CLI + Lightdash CLI -You can use the dbt Fusion CLI (`dbtf`) together with the Lightdash CLI during local development. -The Lightdash CLI does **not** run dbt itself; it relies entirely on the manifest (`manifest.json`) generated by *your* dbt tool. Since dbt Fusion produces a Core-compatible manifest, Lightdash CLI commands (such as `lightdash preview` and `lightdash deploy`) work as expected. +**Local development with Lightdash CLI** +You can use the dbt Fusion CLI (`dbtf`) together with the Lightdash CLI. The Lightdash CLI does not run dbt itself; it simply reads the manifest (`manifest.json`) generated by your dbt tool. Because dbt Fusion produces a Core-compatible manifest, the Lightdash CLI works the same whether you use `dbt` or `dbtf` locally. -### On Lightdash: Why your project still compiles with dbt Core 1.10+ -When you connect your dbt project to Lightdash or trigger a build in the UI, Lightdash compiles your project using **dbt Core 1.10+**, even if you're running Fusion locally. - -This works because: - -- dbt Fusion follows the **same configuration model** as dbt Core 1.10+ (including the `config.meta` structure). -- Fusion outputs a **Core-compatible manifest**, which Lightdash can parse without needing a Fusion runtime. - -### Which dbt version should I choose in the Lightdash UI? -When asked to select a dbt version, choose **dbt Core 1.10+**, even if your local workflow uses dbt Fusion. -Fusion projects are fully compatible with Lightdash’s Core-based compilation as long as the project conforms to the dbt 1.10+ structure. - ---- +**Connecting a Fusion project to Lightdash** +When you connect your dbt project in the Lightdash UI, you will be asked which dbt version your project uses. Since Lightdash compiles your project using **dbt Core 1.10+** on its servers, you should select **dbt Core 1.10+**, even if you use dbt Fusion locally. dbt Fusion follows the same project configuration model as dbt 1.10+ and produces a manifest that Lightdash can compile using Core. ## Recommended Migration Process ### Step 1: Upgrade to dbt 1.10 and Fix Warnings From 295cd97e0f0caddb28c7fc7d124b1546accbcf60 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Wed, 10 Dec 2025 19:05:07 +0000 Subject: [PATCH 7/7] Documentation edits made through Mintlify web editor --- dbt-guides/dbt-fusion-migration.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/dbt-guides/dbt-fusion-migration.mdx b/dbt-guides/dbt-fusion-migration.mdx index a96bb80e..6351d54d 100644 --- a/dbt-guides/dbt-fusion-migration.mdx +++ b/dbt-guides/dbt-fusion-migration.mdx @@ -29,14 +29,14 @@ When you connect your dbt project in the Lightdash UI, you will be asked which d 2. Use Lightdash's [MetaMove CLI](https://docs.lightdash.com/dbt-guides/dbt-1.10-migration#automated-migration-with-metamove) to automatically migrate `meta` and `tags` from top-level properties to `config` blocks. 3. Run your dbt project and address any other deprecation warnings before proceeding. Note you can also use [dbt-autofix](https://github.com/dbt-labs/dbt-autofix) to automatically resolve many deprecation warnings. + + We'll be updating all documentation code snippets to include dbt v1.10+ YAML structure (`config.meta`) soon. + + ### Step 2: Migrate to Fusion (only required for dbt Core users) Once all deprecation warnings are resolved, dbt Core users will need to follow the steps below to migrate to the dbt Fusion engine. dbt Cloud users, however, can wait for automatic rollout - dbt Labs will handle the dbt Fusion migration automatically. #### For dbt Core Users: 1. Check that you meet the [dbt Fusion migration prerequisites](https://docs.getdbt.com/docs/fusion/install-fusion#prerequisites) 2. Install the dbt Fusion engine following the [installation guide](https://docs.getdbt.com/docs/fusion/install-fusion#install-fusion) -3. Run your project with dbt Fusion to identify any compatibility issues. - - - We'll be updating all documentation code snippets to include dbt v1.10+ YAML structure (`config.meta`) soon. - \ No newline at end of file +3. Run your project with dbt Fusion to identify any compatibility issues. \ No newline at end of file