Eric Song04/12/2023, 4:35 PM
Eric Song04/13/2023, 1:27 PM
Dan Rammer (hamersaw)04/13/2023, 1:58 PM
which is set on FlytePropeller and indicates that any cached data older than X should not be used. Unfortunately this is not currently configurable on a per-task basis. This is something we have discussed adding many times - most recently in this issue. • Do we have any control over when cache entries are removed? -- There has been great community involvement here, as this is an issue many people face. The current situation is that Flyte has an
flag that can be set when launching an execution (either from the UI or cli) that indicates that all tasks that are cached should be recomputed and the new results used. Additionally, this issue (and many associated PRs) contains implementation for cache delete over specific executions. So a user (again from the UI or cli) can manually delete all cached data that resulted from a specific execution. We have not merged the cache delete functionality yet, but it is on the roadmap at high priority.
Eric Song04/13/2023, 3:23 PM