falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shwetha G S (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-708) Falcon assumes a default umask in HDFS for staging dir
Date Mon, 22 Sep 2014 05:35:34 GMT

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

Shwetha G S commented on FALCON-708:

We need to fix the file's permissions as well which by default is 644. So, yes its in a lot
of places. As Srikanth pointed out we should move it to a single function. If its a single
function, its easy to make it configurable?

> 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

View raw message