Andras Somi02/20/2023, 10:54 AM
), because the provider might not put down the corresponding file for that week, while the rest of the files is expected to be there for each partition. The optional assets will have gaps in their partition history which in turn seems to turn on the “Stale” flag on the asset (even if the latest partition is green) which will propagate to downstream assets, making a big branch of my assets permanently stale even though we consider them fresh practically. Is there a way to make these optional partitioned assets look fresh if the latest partition was found? Or is it the opposite of what people would expect from a partitioned asset?
Vinnie02/20/2023, 11:13 AM
. I have a similar use case with an asset that needs to be historized but is only irregularly updated. I believe it’s currently undocumented, but I found the code (incl. code example) to be very straightforward: https://github.com/dagster-io/dagster/blob/master/python_modules/dagster/dagster/_core/definitions/partition.py#L538 Alternatively, you could just materialize an empty object when the partition is not present.
Andras Somi02/20/2023, 12:52 PM
Alternatively, you could just materialize an empty object when the partition is not present.That’s what I’m looking into right now, but it feels “dirty”. I also lose some information about the missing partitions. It’s useful to know if one is missing, just don’t want it to make my asset stale if I already have a more recent partition.
looks interesting though. I saw a few discussions earlier around the concept but I didn’t know it’s already implemented to some extent. Thanks for bringing it up!
claire02/21/2023, 9:05 PM
Andras Somi02/21/2023, 10:20 PM
sandy02/23/2023, 4:26 PM
Andras Somi02/23/2023, 4:32 PM
Vinnie02/23/2023, 5:23 PM
sandy02/23/2023, 6:25 PM
Vinnie02/23/2023, 6:28 PM