falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pradeep Bhadani (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1162) Cluster submit succeeds when staging HDFS dir does not have 777 (ALL) permission
Date Fri, 19 Jun 2015 09:17:01 GMT

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

Pradeep Bhadani commented on FALCON-1162:
-----------------------------------------

[~me.venkatr] - permission 777 is all open and might not be good choice when processing sensitive
data. 
What is the motivation behind for going to permission 777 for staging directory?

> Cluster submit succeeds when staging HDFS dir does not have 777 (ALL) permission 
> ---------------------------------------------------------------------------------
>
>                 Key: FALCON-1162
>                 URL: https://issues.apache.org/jira/browse/FALCON-1162
>             Project: Falcon
>          Issue Type: Bug
>          Components: common
>    Affects Versions: 0.6
>            Reporter: Venkat Ramachandran
>            Assignee: Venkat Ramachandran
>            Priority: Blocker
>             Fix For: 0.6.1
>
>         Attachments: FALCON-1162.5.patch, FALCON-1162.7.patch, falcon-1162.1.patch, falcon-1162.2.patch,
falcon-1162.3.patch
>
>
> Staging HDFS dir specified in the cluster definition should have WORLD WRITABLE permission.
It seems Cluster entity submit used to validate this condition in order to avoid further runtime
failures. 
> But, this check had been reverted as part of the FALCON-910 commits (only checks for
755) as below:
> ClusterEntityParser.java   
> {code}
>         checkPathOwnerAndPermission(cluster.getName(),  stagingLocation.getPath(), fs,
HadoopClientFactory.READ_EXECUTE_PERMISSION, false);
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message