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/glossary.md
+15
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,9 @@
3
3
## Abstract Syntax Tree
4
4
A tree representation of the syntactic structure of source code. Each tree node represents a construct that occurs. The tree is abstract because it does not represent every detail appearing in the actual syntax; it also does not have a standard representation.
5
5
6
+
## Automatic Data Rebasing
7
+
When merging in changes from another branch, SQLMesh automatically reads the history of changes and applies the changes and determines what needs to be rebuilt (if anything). This is done by leveraging the change category of each change to determine the lineage of breaking/non-breaking changes and where there might be overlap.
8
+
6
9
## CI/CD
7
10
An engineering process that combines both Continuous Integration (automated code creation and testing) and Continuous Delivery (deployment of code and tests) in a manner that is scalable, reliable, and secure. SQLMesh accomplishes this with [tests](tests.md) and [audits](audits.md).
8
11
@@ -36,12 +39,21 @@ In a full data refresh, a complete dataset is deleted and then entirely overwrit
36
39
## Idempotency
37
40
The property that, given a particular operation, the same outputs will be produced when given the same inputs no matter how many times the operation is applied.
38
41
42
+
## Incremental Loads
43
+
Incremental loads are a type of data refresh that only updates the data that has changed since the last refresh. This is significantly faster and more efficient than a full refresh loads. SQLMesh encourages developers to incrementally load when possible by offering easy to use variables and macros to help define your incremental models. See [Model Kinds](models/model_kinds.md) for more information.
44
+
39
45
## Integration
40
46
Combining data from various sources (such as from a data warehouse) into one unified view.
41
47
42
48
## Lineage
43
49
The lineage of your data is a visualization of the life cycle of your data as it flows from data sources downstream to consumption.
44
50
51
+
## Plan Summaries
52
+
An upcoming feature that allows users to see a summary of changes applied to a given environment.
53
+
54
+
## Semantic Understanding
55
+
SQLMesh, by leveraging [SQLGlot](https://github.com/tobymao/sqlglot), understands the full meaning of a SQL model. That means it can not only validate that what is written is valid SQL but also transpile (convert) that SQL into other engine dialects if needed.
56
+
45
57
## Slowly Changing Dimension (SCD)
46
58
A dimension (in a data warehouse, typically a dataset) containing relatively static data that can change slowly but unpredictably, rather than on a regular schedule. Some examples of typical slowly changing dimensions are places and products.
47
59
@@ -59,3 +71,6 @@ Term used to describes SQLMesh's ability to share tables across environments to
59
71
60
72
## Virtual Update
61
73
Term used to describe a plan that can be applied without having to load any additional data or build any additional tables. See [Virtual Update](plans.md#virtual-update) for more information.
74
+
75
+
## Virtual Preview
76
+
Term used to describe the ability to create an environment without having to build any additional tables. By comparing the version of models in the repo against what currently exists, SQLMesh can create an environment that exactly represents what is in the repo without by just updating views.
0 commit comments