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
+11-10Lines changed: 11 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,23 +43,24 @@ This is a common choice in scenarios such as an addition of a new column, an act
43
43
44
44
If any downstream models contain a `select *` from the model, SQLMesh attempts to infer breaking status on a best-effort basis. We recommend explicitly specifying a query's columns to avoid unnecessary recomputation.
45
45
46
-
### Forward-only change
47
-
A modified (either directly or indirectly) model that is categorized as forward-only will continue to use the existing physical table once the change is deployed to production (the `prod` environment). This means that no backfill will take place.
48
-
49
-
While iterating on forward-only changes in the development environment, the model's output will be stored in either a temporary table or a shallow clone of the production table if supported by the engine.
50
-
51
-
In either case the data produced this way in the development environment can only be used for preview and will **not** be reused once the change is deployed to production. See [Forward-only Plans](#forward-only-plans) for more details.
52
-
53
-
This category is assigned by SQLMesh automatically either when a user opts into using a [forward-only plan](#forward-only-plans) or when a model is explicitly configured to be forward-only.
|[Breaking](#breaking-change)|[Direct](glossary.md#direct-modification) or [Indirect](glossary.md#indirect-modification)|[Backfill](glossary.md#backfill)|
|[Forward-only](#forward-only-change)|[Direct](glossary.md#direct-modification) or [Indirect](glossary.md#indirect-modification)|[No Backfill](glossary.md#backfill), schema change |
53
+
54
+
## Forward-only change
55
+
In addition to categorizing a change as breaking or non-breaking, it can also be classified as forward-only.
56
+
57
+
A model change classified as forward-only will continue to use the existing physical table once the change is deployed to production (the `prod` environment). This means that no backfill will take place.
58
+
59
+
While iterating on forward-only changes in the development environment, the model's output will be stored in either a temporary table or a shallow clone of the production table if supported by the engine.
60
+
61
+
In either case the data produced this way in the development environment can only be used for preview and will **not** be reused once the change is deployed to production. See [Forward-only Plans](#forward-only-plans) for more details.
62
+
63
+
This category is assigned by SQLMesh automatically either when a user opts into using a [forward-only plan](#forward-only-plans) or when a model is explicitly configured to be forward-only.
63
64
64
65
## Plan application
65
66
Once a plan has been created and reviewed, it is then applied to the target [environment](environments.md) in order for its changes to take effect.
0 commit comments