You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Changing start to older date can lead to out-of-order execution & miss intervals #4837
The modified models are disconnected in the evaluation dag: {('"db"."s"."a"', ((1672531200000, 1672617600000), 0)): set(), ('"db"."s"."c"', ((1672531200000, 1672617600000), 0)): set()}. This can lead to out-of-order execution, even though s.c depends on s.a indirectly.
After applying the 2nd plan, I don't see the date 2023-01-01 in either s.b or s.c– only s.a has it. This is a side-effect of the previous bullet, because sqlmesh sees that we've already computed the interval 2023-01-01 for s.b, since it starts earlier than that, so it doesn't recompute it. Hence, s.c, who sources from s.b, ends up with stale data.
Activity
fix(plan): restate downstream intervals when a model's start moves ea…