Skip to content
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.

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

Fix heading and links for loaded_at_field #5207

Merged
merged 7 commits into from
Apr 4, 2024
Merged
Changes from all commits
Commits
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
12 changes: 9 additions & 3 deletions website/docs/reference/resource-properties/freshness.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,8 +62,6 @@ To exclude a source from freshness calculations, you have two options:
- Don't add a `freshness:` block.
- Explicitly set `freshness: null`.

## loaded_at_field
(Optional on adapters that support pulling freshness from warehouse metadata tables, required otherwise.)
</VersionBlock>

<VersionBlock lastVersion="1.6">
Expand All @@ -75,11 +73,19 @@ Freshness blocks are applied hierarchically:
- A `freshness` and `loaded_at_field` property added to a source _table_ will override any properties applied to the source.

This is useful when all of the tables in a source have the same `loaded_at_field`, as is often the case.
</VersionBlock>

## loaded_at_field

<VersionBlock firstVersion="1.7">
(Optional on adapters that support pulling freshness from warehouse metadata tables, required otherwise.)
</VersionBlock>

<VersionBlock lastVersion="1.6">
(Required)
</VersionBlock>
A column name (or expression) that returns a timestamp indicating freshness.

<br/><br/>A column name (or expression) that returns a timestamp indicating freshness.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding the <br/><br/> tags is a little ugly, but it's the only thing I found that would work to preserve the current formatting.

I tried several things to no avail.

If we don't like them, I'd suggest that we merge this PR as-is and create a follow-up to address them.


If using a date field, you may have to cast it to a timestamp:
```yml
Expand Down
Loading