[FLINK-9382] Inconsistent file storage behavior in FileCache

• Type: Bug
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Affects Version/s: 1.6.0
• Component/s: Runtime / Task
• Labels: auto-deprioritized-major auto-deprioritized-minor
• Assignee: Unassigned
• Reporter: Chesnay Schepler
• Created: 16/May/18 12:54
• Updated: 08/Dec/21 10:39

Description

The file storage behavior in the FileCache is inconsistent and depends whether we're accessing a file or zipped folder.

In case of a file we return the file returned from the PermanentBlobService as is, in this case the blobserver takes care of deleting the file at some point.
In case of a directory (that is implicitly zipped!) we extract the zip into a separate storage directory and delete the zip afterwards (the deletion in particular is questionable as it interferes with the blob server).

The underlying issue to me is that the responsibilities between the PermanentBlobService and FileCache aren't clearly laid out, and they actually seem a bit redundant.
We may want to change the FIleCache to be a thin wrapper around the PermanentBlobService that only takes care of unzipping directories and setting executable flags.