Update project for Fusion compatibility#103
Conversation
|
|
@b-per Yes, all good points. I need to do a little more testing with this version in the platform and ensure I can switfly swtich between extended/compatible/latest/latest fusion with little to no friction. Once I've done that:
As for a long-living branch for older versions, I'll defer to you and your team. From the docs side, we're taking the approach to only document and use examples for currently supported versions, which would exclude those older requriements. If you want to keep this Jaffle Shop functional for unsupported versions that still appear in the selection menu, I'm happy to help |
| This README will guide you through setting up the project on dbt Cloud. Working through this example should give you a good sense of how dbt Cloud works and what's involved with setting up your own project. We'll also _optionally_ cover some intermediate topics like setting up Environments and Jobs in dbt Cloud, working with a larger dataset, and setting up pre-commit hooks if you'd like. | ||
|
|
||
| > [!NOTE] | ||
| > **The `main` is compatible with [dbt Fusion](https://docs.getdbt.com/docs/fusion/about-fusion).** and dbt Core v1.12 and higher. It uses the latest Semantic Layer YAML spec, with semantic models embedded in model YAML files, `type: simple` metrics replacing measures, and `type_params` promoted to top-level keys. If you're looking for the legacy project using the pre-Fusion YAML spec, check out the [`jaffle-shop-old`](../../tree/jaffle-shop-old) branch. |
There was a problem hiding this comment.
should be the "main branch" instead of "the main"
There was a problem hiding this comment.
Also instead of "pre-Fusion YAML spec" we should talk about the "legacy YAML semantic layer spec"
b-per
left a comment
b-per
left a comment
There was a problem hiding this comment.
Not a full review yet. But blocking things so far.
- we need a
require-dbt-versionindbt_project.ymlwith dbt 1.12+ range if we use syntax that is only valid for 1.12 and Fusion - BQ CI is failing because
to_dateis not valid. We need a cross warehouse time spine
2 participants
This PR updates the Jaffle Shop project to run without deprecation warnings or errors on both
LatestandFusion Latestin the dbt platform:Latestas well, we will re-introduce in the new formatRan project locally in Fusion with Snowflake and got a successful build with 0 warnings or errors