https://dagster.io/ logo
#ask-community
Title
# ask-community
d

Deividas Jodogalvis

07/18/2023, 10:51 AM
1.3.14 release:
Copy code
[ui] Fixed a bug where selecting partitions in the launchpad dialog cleared out your configuration
I think this or some other changes actually broke `ops`RunConfig population 😬 In 1.3.13 in launchpad I can select multipartition and config yaml gets populated as it should In 1.3.14 it does not work anymore, config yaml is populated with many keys(ops, resources, execution) by default(just like 1.3.13) but selecting a multipartition nothing changes, just “Missing required config entry” at the bottom Scaffold missing config does not help either
a

Alex Kan

07/19/2023, 3:43 PM
+1 on this
m

Michael Kremer

07/19/2023, 3:51 PM
+1 on this
a

Alex Kan

07/19/2023, 3:55 PM
edit: RESOLVED by moving to
context.asset_partition_key_for_output()
We believe that the 1.3.14 update broke the config for our jobs using
@daily_partitioned_config
.
When clicking “materialize all” and selecting a partition in the job view, the config for the ops are empty and don’t follow the config schema. “Scaffold missing config” fills out the schema appropriately, but doesn’t parse the partition as expected within the body of the function we annotate with
@daily_partitioned_config
FWIW we’re using
define_asset_job
within
build_schedule_from_partitioned_job
here
more context on what this setup looks like
d

Deividas Jodogalvis

07/19/2023, 6:21 PM
hi Alex, could you explain more about what do you mean by ? 😄
moving to
context.asset_partition_key_for_output()
a

Alex Kan

07/19/2023, 10:42 PM
My issue may be slightly different than yours as we’re not using multi-partitions. But instead of getting the start/end dates in the function
config
(second screenshot), I used
datetime.strptime(context.asset_partition_key_for_output(), <DATE_FORMAT>)
instead to get the start/end date of the partition to pass to the asset
d

Deividas Jodogalvis

07/20/2023, 7:28 AM
I see, yeah sounds different
2 Views