19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
One question for freshness policies `By 12:01 GMT+...
# dagster-plusg
geoHeil
04/29/2023, 10:46 AMOne question for freshness policies
By 12:01 GMT+2, this asset should incorporate all data up to 24 hours before that time.geoHeil
04/29/2023, 10:46 AMfreshness_cron = "1 12 * * *"
freshness_tz = "Europe/Vienna"
fp = FreshnessPolicy(
maximum_lag_minutes=24 * 60,
cron_schedule=freshness_cron,
cron_schedule_timezone=freshness_tz,
)
geoHeil
04/29/2023, 10:46 AMthis is the related freshness policy
o
owen
05/01/2023, 5:10 PMhi @geoHeil! is this asset downstream of any other assets / source assets? if so, when were those assets materialized?
g
geoHeil
05/01/2023, 8:42 PMIt is the source itself
geoHeil
05/01/2023, 8:43 PMan example/screenshot
o
owen
05/01/2023, 10:36 PMah I see, thanks for the screenshot! for time-partitioned assets, the freshness policy is making a statement about the state of the entire asset, i.e. "incorporate all data up to X time" means "all partitions up to X time should be filled"
g
geoHeil
05/02/2023, 3:43 AMI see. The feature request in dagit to mark partitions which are available outside dagseter as available (or no longer sourcable) will then be needed
o
owen
05/02/2023, 6:38 PMgotcha -- there's not a super clean way of doing this, but it is possible to manually emit those materialization events to tell Dagster that they exist: https://github.com/dagster-io/dagster/discussions/12561