Hi guys! Is there a way to invalidate the cache for a certain input for a task within a workflow, without increasing the cache version/invalidating the cache of other inputs?

hi @Maarten de Jong unfortunately afaik there’s no way to do this for particular sets of inputs. What’s the cost of invalidating the cache for all inputs (i.e. recomputing everything)?

hey, in this particular case it's quite expensive (~15TB of data to redownload and reprocess) but we have a workaround for now, just wanted to make sure we're not missing anything. I could drop a feature request ticket on the github if you think it is technically feasible and relevant

^^ @Eduardo Apolinario (eapolinario) @Ketan (kumare3)?

in the download step, so subsequent processing steps used the corrupt download

@Maarten de Jong how about you run the 6 steps manually

that's what I've been looking into briefly as another workaround for this one instance. as it might become more relevant in future, larger runs, something that doesn't require digging around in a DB manually would be preferred

Or flyteremote- in the node details if it was a cache hit you should see https://github.com/flyteorg/flyteidl/blob/356351fdbf390caf9986474a5fcf9515cf2a6e54/protos/flyteidl/admin/node_execution.proto#L183

yeah definitely for now, thank you

@Ketan (kumare3) I believe I managed to find them that way (looking into the issue with @Maarten de Jong). for the future, having some option/extra checkbox to run without cache via the flyte console would be great, I'll put it onto our internal todo list

Yes please do

sure thing

No I think you should write it

I'll start a draft tomorrow and will probably finish it when I'm back in two weeks then. We'll also have a bit more of a discussion internally what'd be helpful to us