-
Notifications
You must be signed in to change notification settings - Fork 18
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
sqlmesh: small fixes to business logic and date handling #3019
base: main
Are you sure you want to change the base?
Conversation
ccerv1
commented
Feb 11, 2025
- fix(sqlmesh): update onchain models to latest business logic
- fix(sqlmesh): include AA event types
- fix(sqlmesh): update project graphs to latest models
- fix(sqlmesh): final review and trino compatibility checks
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 😄
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.
I think we discussed this at length yesterday, but a summary of what I remember:
- Let's version definitions with explicit dates so that we know what we funded
- I'll work on adding the events we discussed into the event table, so that we can write these models on top of the event table
- We will need to add user AA events into the event table as well, will need your help when we get to that point
- Worth doing a simple token transfer event into the event table as an example
- Eventually, we will need to track funding amounts to a metric_id / metric definition, which is why we probably want to have immutable definitions at the time of funding
- Otherwise looks fine, I'd keep running
@@ -15,7 +14,7 @@ with developers as ( | |||
on events.from_artifact_id = users.user_id | |||
where | |||
events.event_type = 'COMMIT_CODE' | |||
and not regexp_matches( -- TODO: confirm this will work in Trino too |
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.
I don't think so...
https://trino.io/docs/current/functions/regexp.html
Can you
- Replace with valid regexp fn
- Make Trino dialect explicit in model definition
- Test with local Trino?