Mike Zhong
04/25/2022, 4:15 PMcreate_node()
. We have a bunch of @tasks
which have dependencies on one another, but they are not explicit (nothing is returned or passed in). We can easily use the imperative style to define the order of the tasks in a regular @workflow
. Does the imperative style also work for @dynamic
workflows?Samhita Alla
create_node()
works with @dynamic
. It doesn’t work locally cause a dynamic workflow is treated as a task during a local execution; however, it should work on the sandbox and Flyte backend.
cc: @Yee, should we add the support for local runs?Yee
ImperativeWorkflow
object. In the dynamic case, I’m not sure how you’d distinguish between a normal task and an imperative one.Samhita Alla
create_node()
but not the actual ImperativeWorkflow
. I tested this specific use case out by including create_node()
within @dynamic
. It didn’t work locally but worked on sandbox.
If we’re talking about ImperativeWorkflow
, are you asking if we’ve tested this locally as a dynamic workflow? How will we do that?Yee
Samhita Alla
Yee
Mike Zhong
04/26/2022, 4:58 PM