falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-708) Falcon assumes a default umask in HDFS for staging dir
Date Fri, 19 Sep 2014 06:12:35 GMT

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

Srikanth Sundarrajan commented on FALCON-708:
---------------------------------------------

{code}
+            FsPermission permission = new FsPermission(
+                    FsAction.ALL, FsAction.READ_EXECUTE, FsAction.NONE);
+            fs.setPermission(outPath, permission);
{code}

This snippet is too many places, can we move this to a single function, so that changes to
this can be controlled from one place.

> Falcon assumes a default umask in HDFS for staging dir
> ------------------------------------------------------
>
>                 Key: FALCON-708
>                 URL: https://issues.apache.org/jira/browse/FALCON-708
>             Project: Falcon
>          Issue Type: Bug
>          Components: oozie
>    Affects Versions: 0.6
>            Reporter: Venkatesh Seetharam
>            Assignee: Venkatesh Seetharam
>            Priority: Critical
>             Fix For: 0.6
>
>         Attachments: FALCON-708-v1.patch, FALCON-708.patch
>
>
> Falcon needs to have 750 on staging so oozie can read workflow definitions. If the default
umask is changed, falcon becomes unusable and workflows cannot be scheduled.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message