CM
06/11/2021, 8:29 PMKevin Kho
06/11/2021, 8:30 PM--force
option. I think this might be related to this issueCM
06/11/2021, 8:33 PMKevin Kho
06/11/2021, 8:37 PMflow.serialize()
, you’ll find the executor is not there. This is because executor and results can contain sensitive information so we don’t keep them in the flow schema.idempotency_key
here to force the registration. You can see this in the register
method here: https://docs.prefect.io/api/latest/core/flow.html#flow-2CM
06/11/2021, 8:42 PMKevin Kho
06/11/2021, 8:42 PMCM
06/11/2021, 8:43 PMKevin Kho
06/11/2021, 8:48 PMprefect register flow
command have a force
option on that version?CM
06/11/2021, 8:52 PMKevin Kho
06/11/2021, 8:57 PMCM
06/11/2021, 8:58 PMKevin Kho
06/11/2021, 9:00 PMflow.register()
and then python myflow.py
to register, I get the version bumped.CM
06/11/2021, 9:01 PMKevin Kho
06/11/2021, 9:04 PM--force
version in the future. If you can’t, I would honestly try altering the Flow a little bit, maybe adding a log statement somewhere to force the metadata to change and I think that would force the re-registration.CM
06/11/2021, 9:05 PMKevin Kho
06/11/2021, 9:09 PMpython myflow.py
does take effect. I changed from LocalDaskExecutor to LocalExecutor. You can run the flow with DEBUG logs to see the executor type.CM
06/11/2021, 9:13 PMKevin Kho
06/11/2021, 9:17 PMCM
06/11/2021, 9:32 PMKevin Kho
06/11/2021, 9:38 PMCM
06/11/2021, 9:40 PMKevin Kho
06/11/2021, 9:41 PMquery {
flow_run(where: { id: {_eq: "160d2a2b-58e1-442a-818d-2855f283ac6d"} }) {
id
flow_id
flow {
name
version
}
}
}
CM
06/11/2021, 9:43 PM