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

Gerben van der Huizen

10/12/2022, 2:32 PM
Hi Dagster team, I recently upgraded the
dagster/dagster-k8s
image we are using from
0.14.9
to
1.0.12
. After running
dagster instance migrate
it seemed that all our ops, jobs, schedules etc. were all still intact and working fine. However, when browsing through the schedules interface I noticed that the
Partition Set
was no longer being displayed (given a
None
value) . I can still view all the partitions when I navigate to the run view of individual jobs + the
partition_set
column in the
runs
table seems to be filled as well. Are we missing some migration step for this particular field? Or maybe we need to add some additional config to the job in the repository?
2
Anyone encountered this before when migrating to 1.0+? What are we missing?
c

chris

10/18/2022, 12:05 AM
Hey Gerben - I was able to reproduce this, I think it's an oversight. Filed an issue: https://github.com/dagster-io/dagster/issues/10060 .
Just to confirm, the jobs that are being scheduled, they have partitioned config associated with them yes?
g

Gerben van der Huizen

10/18/2022, 6:50 AM
@chris Yes, jobs are still being scheduled and we are using a
daily_partitioned_config
for all of them. Thank you for creating the issue.
c

chris

10/18/2022, 5:43 PM
gotcha. Thanks for the report