sticky-angle-28419
04/21/2023, 3:59 PMglamorous-carpet-83516
04/21/2023, 4:10 PMsticky-angle-28419
04/21/2023, 4:12 PMglamorous-carpet-83516
04/21/2023, 5:23 PMglamorous-carpet-83516
04/21/2023, 5:27 PMsticky-angle-28419
04/21/2023, 5:38 PMrequests
lib, etc)?. And then if I process it and send it to another task, then flyte will take care of creating the reference for the s3 data and I can just use it in the second task as if it’s already in memory?glamorous-carpet-83516
04/21/2023, 6:06 PMfile.download()
, file.open()
or __fspath__
glamorous-carpet-83516
04/21/2023, 6:07 PMfile.open()
return file handler, and you can read streaming datasticky-angle-28419
04/21/2023, 6:18 PMsticky-angle-28419
04/21/2023, 6:37 PMsticky-angle-28419
04/21/2023, 6:37 PMglamorous-carpet-83516
04/21/2023, 10:03 PMglamorous-carpet-83516
04/21/2023, 10:03 PMsticky-angle-28419
04/21/2023, 10:05 PMsticky-angle-28419
04/22/2023, 1:25 AM@task
, do all flyte tasks in the same workflow share that storage?glamorous-carpet-83516
04/23/2023, 1:01 AMsticky-angle-28419
04/23/2023, 1:04 AMpreprocess_task
-> train_task
, and download in preprocess_task
to do some data processing and pass it over to train_task
, then will Flyte basically upload the processed data from the first task to s3 and then download that data in train_task
?glamorous-carpet-83516
04/23/2023, 1:04 AMsticky-angle-28419
04/23/2023, 1:05 AMsticky-angle-28419
04/23/2023, 1:05 AMsticky-angle-28419
04/23/2023, 1:06 AM