https://flyte.org logo
#announcements
Title
# announcements
s

Sören Brunk

03/17/2022, 10:10 AM
Quick question about flyte remote. I have a workflow that produces a
FlyteDirectory
as final output. Via flyteconsole/API I get a reference to the object, like so:
Copy code
o0:
  type:
    multi-part
  uri:
    <gs://flyte-bucket/data/q1/pjziwgu55i-n1-0/48f7d1af2f65a6ff4c03fac9191cbea9>
If I try to fetch that workflow via
FlyteRemote
I get a local path as output. It's empty though.
Copy code
remote = FlyteRemote.from_config()
exec = remote.fetch_workflow_execution("abc")
print(exec.outputs)
// /tmp/flyte3eg_mcpz/control_plane_metadata/local_flytekit/6f2223e1c864f6d1e88c8dbad090f349
What is the purpose of this local path and is there a way to get the original output location via
FlyteRemote
?
k

Ketan (kumare3)

03/17/2022, 1:59 PM
@Yee Soren hold tight for 2 weeks. We are updating Flyte remote. It currently eagerly loads
We are changing to lazy and the entire api is getting a refresh
👍 1
s

Sören Brunk

03/17/2022, 2:02 PM
Cool, thanks!
y

Yee

03/17/2022, 6:04 PM
inside the object, the
_remote_source
field (there might be a
remote_source
property) should have the original path.
but yeah we’re changing the interface so that it doesn’t turn the
Blob
literal into a
FlyteFile
local object.
but that might be irrelevant to this discussion. the object already does lazy downloading.
it won’t download anything until you call
download()
on it, or try to
open
it
👍 1
s

Sören Brunk

03/17/2022, 7:27 PM
Ah I didn't realize I can just call
download()
on the output being a
FlyteDirectory
! Thanks @Yee
t

Thomas Vetterli

03/17/2022, 7:43 PM
Is the api change going to contain some breaking changes?
y

Yee

03/17/2022, 7:52 PM
there will be some yeah, but hopefully not too bad. The whole FlyteRemote experience was never really dialed in we think. We recently revamped the configuration of flytekit as well which affects this as well.
cc @Ketan (kumare3)
t

Thomas Vetterli

03/17/2022, 7:55 PM
looking fwd
75 Views