Selective Delayed Query Invalidation for Concurrent(large file upload) Mutations in RTK Query

[pugsh]

I was working on a file upload feature using RTK Query with automatic query invalidation. The feature refreshes the uploaded files list once a file upload is completed. However, when multiple files of varying sizes are uploaded simultaneously, an issue occurs. The upload API (mutation with a PUT call) and the list query use different tags. The list query invalidation waits for all mutation queries to complete, causing delays. Switching to immediate query invalidation is not feasible due to the risk of introducing stale data.

A mechanism for selective delayed query invalidation, targeting only the tags associated with pending queries, would help here.

Is this possible now?

[phryneas]

No, there is currently no such feature.

A mechanism for selective delayed query invalidation, targeting only the tags associated with pending queries, would help here.

Unfortunately, this is also quite problematic - since tags can rely on the response of a mutation, we can't know them yet while the mutation is still in progress - and as a result, we also can't make this distinction beforehand.

[pugsh]

Thanks @phryneas for responding. I understand the complexity here. There is one more case related to the upload, if any application is uploading a large file which takes good amount of time, it will block the automatic query invalidation for the whole app until the upload is complete.

Is it feasible to do some exception in such scenarios, delayed invalidation should not wait for some mutations or queries?

[phryneas]

Right now, there's no such feature. Generally, I'd recommend to sidestep RTKQ for things like file uploads since you probably want to track upload progress manually anyways.