loaded_at_field
not required for source freshness checks as-of 1.7
#4615
Labels
content
Improvements or additions to content
improvement
Use this when an area of the docs needs improvement as it's currently unclear
priority: high
Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows
size: x-small
This change will take under 3 hours to fix.
source freshness
Contributions
Link to the page on docs.getdbt.com requiring updates
https://docs.getdbt.com/reference/resource-properties/freshness
What part(s) of the page would you like to see updated?
Two things:
loaded_at_field
in order to calculate freshness and which can be calculated from metadata.Platforms that support freshness from metadata
Currently, only Snowflake can calculate from metadata, but consult the following list of issues to track if other adapters add support:
Achieving a mix of null and non-null for
loaded_at_field
dbt-labs/dbt-core#9320 (comment)
Additional information
Additional information can be found in the following places:
Instigating issue
This came up during discussion of this regression: dbt-labs/dbt-bigquery#1044
We have information related to
loaded_at_field
vs. database metadata in the upgrade guide, but we don't yet have it within the docs forfreshness
.The text was updated successfully, but these errors were encountered: