Channels
announcements
ask-the-community
auth
conference-talks
contribute
databricks-integration
datahub-flyte
deployment
ecosystem-unionml
engineeringlabs
events
feature-discussions
flyte-bazel
flyte-build
flyte-console
flyte-deployment
flyte-documentation
flyte-github
flyte-ui-ux
flytekit
flytekit-java
flytelab
great-content
hacktoberfest-2022
helsing-flyte
in-flyte-conversations
integrations
introductions
jobs
konan-integration
linkedin-flyte
random
ray-integration
ray-on-flyte
release
scipy-2022-sprint
show-and-tell
sig-large-models
torch-elastic
workflow-building-ui-proj
writing-w-sfloris
Title
r
Rupsha Chaudhuri
06/27/2022, 4:41 PMHi team... quick question. If a task calls a task, do they both not show up in the Flyte console? I only see the outer task
y
Yee
06/27/2022, 5:08 PMthis isn’t really a supported pattern yet. we should support this though.
but yeah, even if/when we do, it will not show up
tasks are generally not allowed to call other tasks as tasks are supposed to be the atomic unit of work in flyte.
so if you want this kind of a pattern it’s best to use sub-workflows/dynamic tasks
r
Rupsha Chaudhuri
06/27/2022, 5:09 PMwill do.. thanks.. let me update my code in that case
it does appear to work though 🙂
y
Yee
06/27/2022, 5:10 PMoh good
yeah if it works then it’s just calling the function like a normal python function (i hope)
r
Rupsha Chaudhuri
06/27/2022, 5:11 PMI believe so
y
Yee
06/27/2022, 5:11 PMagain there’s no unit tests for this… but when we add them that’s what we’ll be shooting for
r
Rupsha Chaudhuri
06/27/2022, 5:11 PMthat was the intention anyways
thanks for the clarification