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/concepts/plans.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,6 +76,13 @@ To create a forward-only plan, the `--forward-only` option has to be added to th
76
76
sqlmesh plan --forward-only
77
77
```
78
78
79
+
### Effective date
80
+
Changes that are part of the forward-only plan can also be applied retroactively to the production environment by specifying the effective date:
81
+
```bash
82
+
sqlmesh plan --forward-only --effective-from 2023-01-01
83
+
```
84
+
This way SQLMesh will know to recompute data intervals starting from the specified date once forward-only changes are deployed to production.
85
+
79
86
## Restatement plans
80
87
There are cases when models need to be re-evaluated for a given time range, even though changes may not have been made to those model definitions. This could be due to an upstream issue with a dataset defined outside the SQLMesh platform, or when a [forward-only plan](#forward-only-plans) change needs to be applied retroactively to a bounded interval of historical data.
"Enter the effective date (eg. '1 year', '2020-01-01') to apply forward-only changes retroactively or blank to only apply them going forward once changes are deployed to prod"
0 commit comments