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-on-gcp
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
Powered by
Title
l
Louis DiNatale
11/22/2022, 6:19 PM
When you use the clone execution will this use the cache from the previous execution?
y
Yee
11/22/2022, 6:45 PM
you’re referring to the
(cache=True, cache_version="v1")
args to the decorators?
yes - that feature should be independent of execution cloning.
l
Louis DiNatale
11/22/2022, 6:46 PM
Ok so the cache will hold awsome thanks!
y
Yee
11/22/2022, 6:47 PM
assuming the previous execution or some previous execution wrote the cache, yeah, it will hold.
l
Louis DiNatale
11/22/2022, 6:47 PM
Thanks
#ask-the-community
Join Slack