[
https://issues.apache.org/jira/browse/FALCON-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163155#comment-14163155
]
Venkatesh Seetharam commented on FALCON-753:
--------------------------------------------
bq. Does this jira require staging to be 777 and working to be 755 ?
Yes.
bq. What are the effects of this change with respect to compatibility. Meaning,
when users deploy this version of falcon, what needs to be fixed?
Just change the staging and working to be 777 and 755 respectively and we
should be good. We can solve this by adding a config store listener and change
this if not already on reload for backwards compatibility.
> Change the ownership for staging dir to user submitting the feed
> ----------------------------------------------------------------
>
> Key: FALCON-753
> URL: https://issues.apache.org/jira/browse/FALCON-753
> Project: Falcon
> Issue Type: Sub-task
> Components: oozie
> Affects Versions: 0.6
> Reporter: Venkatesh Seetharam
> Assignee: Venkatesh Seetharam
> Labels: backward-incompatible
> Fix For: 0.6
>
> Attachments: FALCON-753-review-v1.patch, FALCON-753-review.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
