-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add: sqlmesh key_metrics
model
#2584
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Auto-approved! please merge responsibly 😄
Test deployment unnecessary, no dbt files have been changed. |
These changes are good! I actually had a slightly different idea but I think we should merge this first as this will work and pragmatically it makes the most sense. I think this depends on some docs and clean up that I need to do. Here's what I was hoping: I was hoping though that we could just write a single metric model. These changes work but my vision for this would definitely require a deeper refactor of the factory. Here's the idea:
This would then instead look like this in
If we do this we would need to change a bit of how the Sooo.... I will make a follow on issue for this :), but I think we can wrap up anything needed with the current PR and merge it! |
Oh also, I'm going to start writing an issue as a design doc for semantic models in sqlmesh. If we did that, then all of this is moot as we could handle that automatically (I think) |
This PR closes #2268. WIP.