falcon-dev mailing list archives

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

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

Venkatesh Seetharam commented on FALCON-708:
--------------------------------------------

bq. Can we make the others permission configurable with default of 0?
This is hard, there are too many pieces and non trivial to address quickly.

bq.  I think the staging path is owned by falcon. 
Yes.

bq. we should change it to user.
The problem is this is insufficient. Falcon also needs access to this to serialize definitions
and then its also being used in OozieWorkflowEngine. logs is another issue which is used by
both falcon and oozie workflows

> 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