Fix: Improve the inference of the default plan start for new models for which cron is not aligned with interval unit boundary #3758
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
…or which cron is not aligned with interval unit boudary
tobymao
approved these changes
Jan 31, 2025
izeigerman
added a commit
that referenced
this pull request
Jan 31, 2025
…or which cron is not aligned with interval unit boundary (#3758)
treysp
pushed a commit
that referenced
this pull request
Jan 31, 2025
…or which cron is not aligned with interval unit boundary (#3758)
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.
When adding a new model while simultaneously modifying a forward-only model, SQLMesh may infer an incorrect default start date for the plan if the new model's cron is not aligned with the interval unit's boundary.