Yes, you can specify task dependencies in Flyte even when there is no data dependency by using the right-shift operator (>>) to chain tasks. This operator enforces execution order without requiring data to flow between tasks. For example, t1 >> t2 ensures t2 runs after t1, regardless of their inputs or outputs. This is supported in the Flyte Python SDK and is useful for setup/teardown patterns or enforcing order for side-effect tasks, as shown in the
Flyte documentation.
If you want a code example or more detail on how to implement this, let me know.
Sources:
-
Flyte documentation: Decorating workflows 👍 0 button 👎 0 button 💡
Hint: Mention @runllm in the thread for followups.