[jira] [Resolved] (FLINK-852) DistributedCache doesn't preserve executable flag

Posted by Shang Yuanchun (Jira) on Jun 18, 2014; 1:04pm
URL: http://deprecated-apache-flink-mailing-list-archive.368.s1.nabble.com/jira-Resolved-FLINK-852-DistributedCache-doesn-t-preserve-executable-flag-tp435.html


     [ https://issues.apache.org/jira/browse/FLINK-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Metzger resolved FLINK-852.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.6-incubating
         Assignee: Chesnay Schepler

Has been resolved by https://github.com/apache/incubator-flink/pull/3

> DistributedCache doesn't preserve executable flag
> -------------------------------------------------
>
>                 Key: FLINK-852
>                 URL: https://issues.apache.org/jira/browse/FLINK-852
>             Project: Flink
>          Issue Type: Improvement
>            Reporter: GitHub Import
>            Assignee: Chesnay Schepler
>              Labels: github-import
>             Fix For: pre-apache, 0.6-incubating
>
>
> all files distributed with the DistributedCache are marked as not executable, which causes a problem for the python interface. (I currently try to package all scripts/dependencies into binaries and distribute those, since we cant distribute directories).
> a fix for this would to to modify Filecache.CopyProcess.call() to include
> ```
> new File(tmp.toString()).setExecutable(true);
> ```
> but this is more of a shotgun approach, since now all files are executable. Is this an acceptable solution?
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/stratosphere/stratosphere/issues/852
> Created by: [zentol|https://github.com/zentol]
> Labels: enhancement, user satisfaction,
> Milestone: Release 0.5.1
> Created at: Sat May 24 13:44:04 CEST 2014
> State: open

--
This message was sent by Atlassian JIRA
(v6.2#6252)