The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Looking for suggestions: I'd like to make sure an `asset` is materialized at least every hour, either through reconciliation with upstream, or through some other mechanism. What is the best mechanism to use?

Looks like `FreshnessPolicy` is not right, nor is an `asset_sensor`

I would use a FreshnessPolicy, what is your concern there though?

The goal here is to ensure that for assets `A -&gt; B` where `B` is downstream of `A`, `B` is materialized every 24h even if `A` is _not_, because the upstream data hasn't changed.

Using a `FreshnessPolicy`  of 24h, `B` still shows as late because its upstream dependency is older than 24h

Hey Gabe - making FreshnessPolicies respect versions is on our near-term roadmap.

In the mean time, I think you'd basically need to write your own sensor to implement this behavior.

Curious - if `A` doesn't change, why do you want `B` updated? Does `B` depend on other data that does change?

`B` is a calendar-week filtered view of `A`, so as time passes `B` will change without the upstream source data changing

gotcha - I'll think a little about how to fit this into the freshness framework

cc <@U01J51Y6B9D>