When using MultiPartitionDefinition with a date and a static field. If we try to access the partition of the run with

asset_partition_key_range

we end up with

PartitionKeyRange(start='2020-12-18|Something_Static', end='2023-03-22|Something_else_static')

Since it’s a list of static elements, there’s no way to all the

static

elements of that run right? Precision I’m trying to run multiple partitions in a

Single Run

Hi Jacob. You can do something like this:

key.keys_by_dimension[static_dimension_name] for key in context.asset_partition_keys_for_output

to get just the static partition keys

Thank you very much this helps a lot. Another thing links to that. I couldn’t find documentation on how to structure the return object when starting a job in a

Single Run

with multiple partitions. Do you have any docs you can send me or a draft version of code. Like do I need to use the

Ouput

object and specify which dict is linked to which partition?

So if you just yield outputs as normal, i.e.

@asset(partitions_def=...)
def my_asset():
    return 1

and you select a range of partitions to execute on, dagster will automatically yield a materialization per partition for the same output