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?

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

The goal here is to ensure that for assets

A -> B

where

B

is downstream of

A

,

B

is materialized every 24h even if

A

is not, because the upstream data hasn't changed.

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.

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 @owen