[
https://issues.apache.org/jira/browse/FALCON-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046480#comment-15046480
]
sandeep samudrala commented on FALCON-1649:
-------------------------------------------
Balu Vellanki added a comment - 3 days ago - edited
Pallavi Rao and Peeyush Bishnoi :
While Pallavi's solution is good, it can introduce failures during concurrent
entity schedule requests. I think we should not introduce potential failures ,
and use 777 when
Multiple users belonging to different groups need rw permissions to the same
dir.
If the data under this dir is lost, it can be recovered.
the data written under this dir does not have to be secure
The staging dir is only used when scheduling an entity. Accidental deletion
(which is an extremely rare scenario) of data under this dir does not break any
scheduled feed/process. When a feed/process is re-scheduled, the staging dirs
will be created again.
Peeyush Bishnoi added a comment - 3 days ago - edited
Balu Vellanki I think we should have more discussion about assigning 777 on
directory <staging_dir>/falcon/workflows/(feed,process) to have some concrete
approach. As assigning 777 can potentially cause data deletion by any random
user and further instances execution will not happen.
> 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
(v6.3.4#6332)
