Is there a particular reason that a partitioned asset can't accept a partitioned asset with a different upstream partition definition? For a non-partitioned downstream asset, the default IO Manager simply gives you a dictionary of partitions by key. Seems like that could be enabled for partitioned downstream assets too? For example, if the upstream asset is partitioned on space, or some static partition definition, a downstream monthly partitioned asset may actually need to scan the entire upstream asset to do some joins or map/reduce.

I think you can accomplish this if you set

AllPartitionMapping

you can also use `non_argument_deps`to logically link but not actually load the asset at runtime

You can build your own PartitionMapping as an interim fix. This isn't yet supported by dagster though. I shared some code somewhere else for the partitioin mapping i built

Thanks all, think we are going to try

AllPartitionMapping

for now. My team is disinclined to use a custom partition mapping given the warning that the API is subject to change on a whim. For the

non_argument_deps

options, we do actually need the read in the asset as runtime to do an in memory join.