Skip to content

freshness is a config now, not a property #8066

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Oct 27, 2025
Merged

freshness is a config now, not a property #8066

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
d32ee8d
freshness is a config now, not a property
graciegoheen Oct 21, 2025
74d2441
clarify exposure property
graciegoheen Oct 21, 2025
147c818
Merge branch 'current' into fix/freshness_is_a_config_now
mirnawong1 Oct 27, 2025
fa8d903
Update define-properties.md
mirnawong1 Oct 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions website/docs/reference/configs-and-properties.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,7 @@ A rule of thumb: properties declare things _about_ your project resources; confi
For example, you can use resource **properties** to:
* Describe models, snapshots, seed files, and their columns
* Assert "truths" about a model, in the form of [data tests](/docs/build/data-tests), e.g. "this `id` column is unique"
* Define pointers to existing tables that contain raw data, in the form of [sources](/docs/build/sources), and assert the expected "freshness" of this raw data
* Define official downstream uses of your data models, in the form of [exposures](/docs/build/exposures)
* Define official downstream uses of your data models, in the form of [exposures](/docs/build/exposures), and assert an exposure's "type"

Whereas you can use **configurations** to:
* Change how a model will be materialized (<Term id="table" />, <Term id="view" />, incremental, etc)
Expand Down
Loading