Semantic model configs in project.yml #4144
Merged
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
github-actions
bot
added
content
mirnawong1
reviewed
Sep 28, 2023
| @@ -105,6 +105,29 @@ semantic_models: | |||
| type: categorical | |||
| ``` | |||
|
|
|||
| <VersionBlock firstVersion="1.7"> | |||
|
|
|||
| Semantic models support configs in either the schema file or at the project level. | |||
There was a problem hiding this comment.
non-blocker question - are we still using schema file or properties.yml file per this doc? I'm a little confused as to what to use
mirnawong1
approved these changes
Sep 28, 2023
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.
What are you changing in this pull request and why?
Semantic model configs for dbt project.yml
Closes: #3997
Checklist
Uncomment if you're publishing docs for a prerelease version of dbt (delete if not applicable):
Add versioning components, as described in Versioning Docs
Review the Content style guide and About versioning so my content adheres to these guidelines.
Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."