You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2018/06/15 14:48:00 UTC

[jira] [Commented] (FLINK-9382) Inconsistent file storage behavior in FileCache

    [ https://issues.apache.org/jira/browse/FLINK-9382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16513916#comment-16513916 ] 

Till Rohrmann commented on FLINK-9382:
--------------------------------------

I would not see this bug a release blocker since it has been like this for a bit.

> Inconsistent file storage behavior in FileCache
> -----------------------------------------------
>
>                 Key: FLINK-9382
>                 URL: https://issues.apache.org/jira/browse/FLINK-9382
>             Project: Flink
>          Issue Type: Bug
>          Components: Local Runtime
>    Affects Versions: 1.6.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>             Fix For: 1.6.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)