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
Ketan (kumare3)
01/03/2023, 3:23 AM
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
Ophir Yoktan
01/03/2023, 5:03 AM
Can you point me to a reference about the 1st option?