My use case is as follows: the initial task of th...
# ask-the-community
o
My use case is as follows: the initial task of the flyte workflow extracts a dataset * in production, I want to always use the latest data (or use cache with short expiration * during development, runtime is more important then data freshness - so I prefer to use cached dataset is there an option to control somehow the caching when launching a workflow (and not just when defining the workflow) Cross posting: https://stackoverflow.com/q/74984146/590335
k
Yes cache can be disabled per workflow execution
A better way would be to use a changeable input value, this might give finer control
o
Can you point me to a reference about the 1st option?
k
If you look at the executionCreateRequest - https://docs.flyte.org/projects/flyteidl/en/latest/protos/docs/admin/admin.html#executionspec - it has an
overwrite_cache
cache flag
but it seems not from the ui yet
128 Views