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
Copy file name to clipboardExpand all lines: docs/guides/linter.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ Here are all of SQLMesh's built-in linting rules:
75
75
|`noselectstar`| Stylistic | The query's top-level selection may not be `SELECT *`, even if SQLMesh can expand the `SELECT *` into individual columns |
76
76
|`nomissingaudits`| Governance | SQLMesh did not find any `audits` in the model's configuration to test data quality. |
77
77
|`nomissingexternalmodels`| Governance | All external models must be registered in the external_models.yaml file |
78
-
|`cronvalidator`| Governance | Upstream model has a cron expression with longer intervals than downstream model. |
78
+
|`cronvalidator`| Governance | Upstream model has a cron expression with longer intervals than downstream model. Example: step_1(`@weekly`) -> step_2(`@daily`) -> step_3(`*/5 * * * *`). step_2 and step_3 are anchored to step_1's cron and will run on the same schedule as step_1. The fix is to align the schedules where a downstream model's cron is the same or has a longer cron interval than an upstream model's.|
0 commit comments