What is the recommended approach to passing large ...
# flyte-support
m
What is the recommended approach to passing large files between container tasks? i.e. would it be sufficient to simply return the file content as a string, and then pass that to the next task as input?
g
f
@many-pharmacist-13114 the idea is to return files directly and let the framework handle it
not content
m
Is there an example of this used with container tasks? Trying to understand how this will interact with the inputs/outputs params in the ContainerTask class
d
container task doesn't support flytefile in remote now I guess
I can support it
wait, flytefile is supported, but flytedirectory is not
You can test it locally, then test it remotely