[
https://issues.apache.org/jira/browse/FALCON-1649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15046481#comment-15046481
]
sandeep samudrala commented on FALCON-1649:
-------------------------------------------
Pallavi Rao added a comment - Yesterday
Balu Vellanki, I know companies where 777 permission is treated as a security
violation. So, in the longer run it may not be good to enforce this requirement.
Another approach could be that Falcon can ensure (with checks) to see if it can
"write" to the appropriate staging dir. Leave it up to the admin to decide how
he/she wants to provide that permission. It could either be that:
1. They provide 777 permission.
2. They could add "falcon", "user1", "user2" etc. to a group (lets say,
"falcon_users") and give the dir 775 permission.
Having said that, I don't want to block this JIRA because the 777 permission is
not introduced by this JIRA. It has been an existing limitation/requirement.
This JIRA only extends it to sub-directories. We can file another JIRA to get
rid of this requirement and move forward with this patch. Sounds good?
> 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)
