Add dbt Fusion CLI and compilation clarifications #269
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-Authored-By: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>
dbt-guides/dbt-fusion-migration.mdx
Outdated
|
|
||
| ### 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. |
Contributor
There was a problem hiding this comment.
@torimwhaley this means they need to have both dbt core and dbt fusion installed right? I just had an issue where i had to downgrade to core because I couldn't generate a preview using fusion.
torimwhaley
requested changes
Dec 10, 2025
| dbt Fusion is compatible with Lightdash for both local development and cloud-based compilation, but a few behaviors differ from dbt Core. | ||
|
|
||
| **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. |
Contributor
Contributor
There was a problem hiding this comment.
Can we confirm why Fusion’s manifest format is compatible with compilation using dbt Core on Lightdash servers? I want to validate this assumption before finalizing the docs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added two new sections to clarify how Lightdash works with dbt Fusion: CLI compatibility and Core v1.10+ compilation behavior. These sections explain that Lightdash CLI works seamlessly with Fusion projects and that Lightdash always compiles using dbt Core v1.10+ regardless of local Fusion usage.
Created by Mintlify agent
fixes: #266