Hard time trying to understand the traceability of tasks on the flow graph #11681
Unanswered
hugocatlas
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello Prefect team,
I'm having a hard time trying to understand how to "force" tasks to be linked together on the flow graph.
Take a look at the following flow snippet:
The
DataGovernanceTasks.get_content_from_s3
task returns a tuple containing three lists that are further consumed by theDataGovernanceTasks.get_items_awaiting_merging
task. The latter returns a dictionary that is further consumed byDataGovernanceTasks.merge_parquet_files_in_path
task.On the flow graph, I have the following:
As you can see,
get_items_awaiting_merging
is correctly displayed and linked to the downstream tasks. However, this doesn't happen toget_content_from_s3
task.In other situations, I have found my way around "forcing" these connections. But in this case, I really don't understand what is blocking.
Could you please clarify what it takes so that the flow graph correctly displays the tasks dependencies?
Cheers,
Hugo
Beta Was this translation helpful? Give feedback.
All reactions