falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sandeep samudrala (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1649) 777 permission issue on staging directory and on subdirectory
Date Tue, 08 Dec 2015 07:08:11 GMT

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

sandeep samudrala commented on FALCON-1649:

Just by taking a step back, why should the directories be owned by the user who submitted
it and why not falcon own it completely. In long run, Falcon should accept the changes (updates,schedules,submits,changes
in lib paths) and mimic them in the staging directory, which cannot be modified by end user.
In this way, Falcon will show various versions of how the mutations have happened over the
time and avoid any accidental deletions or any other issues. Falcon should own the directories.
Please comment/suggestions on the same.

>  777 permission issue on staging directory and on subdirectory
> --------------------------------------------------------------
>                 Key: FALCON-1649
>                 URL: https://issues.apache.org/jira/browse/FALCON-1649
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: sandeep samudrala

This message was sent by Atlassian JIRA

View raw message