[
https://issues.apache.org/jira/browse/FALCON-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14141141#comment-14141141
]
Venkatesh Seetharam commented on FALCON-708:
--------------------------------------------
[~arpitgupta], [~sriksun], what are your thoughts on resolving this.
My thinking was that this can be resolved in 2 phases:
1. make sure the dirs created by falcon have 750 - this jira addresses this only
2. rethink how we should model staging, working and logs dir that needs to be
read by user, falcon with out leaving a hole
staging - falcon has to write and read, user will only read from with in oozie
working - falcon has to write and read, user will only read from with in oozie
logs - falcon reads it, user in oozie writes
Thoughts?
> 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)
