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
f
freezing-airport-6809
01/03/2023, 3:23 AM
Yes cache can be disabled per workflow execution
freezing-airport-6809
01/03/2023, 3:24 AM
A better way would be to use a changeable input value, this might give finer control
c
chilly-bird-33083
01/03/2023, 5:03 AM
Can you point me to a reference about the 1st option?