Feat!: print auto-restated trigger of model evaluation in debug console #4980
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
828ab26 to
1230edb
Compare
|
Nice, I think this will help a lot with debugging "why do I have a heap of changed models, I didnt change anything"-type questions |
1230edb to
37f6fa4
Compare
c605eeb to
a01cb9f
Compare
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.
During a
run, models are usually evaluated because their cron has elapsed. However, any model that is auto-restated will cause all its children to be evaluated as well.Currently, the SQLMesh does not indicate which of those caused the model to be evaluated. This PR adds that information to the debug console.
Example
Consider a project with three models
incremental_model-->full_model-->full_model_downstream.The
incremental_modelhas an auto-restatement, and when it is triggered during a run each of the three models will be annotated withevaluation_triggered_by="db"."sqlmesh_example"."incremental_model":