[ https://issues.apache.org/jira/browse/MAPREDUCE-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653007#comment-13653007 ]
Harsh J commented on MAPREDUCE-5210: ------------------------------------ Changing the FileSystem interface would amount to an incompatible change. Must we really introduce an API for an assumed functionality? Has someone also checked if the original description (which is a check that came in with MR security I think, but has no condition wrap) is the only point of issue or if there are other points where things have to be conditionally wrapped to support a non-true-DFS like S3 to _run_ MR (should we support that)? > Job submission has strict permission validation > ----------------------------------------------- > > Key: MAPREDUCE-5210 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5210 > Project: Hadoop Map/Reduce > Issue Type: Bug > Reporter: Amareshwari Sriramadasu > Assignee: samar > > The following code in JobSubmissionFiles.java mandates strict permission on > job submission : > {noformat} > if (fs.exists(stagingArea)) { > FileStatus fsStatus = fs.getFileStatus(stagingArea); > String owner = fsStatus.getOwner(); > if (!(owner.equals(currentUser) || owner.equals(realUser))) { > throw new IOException("The ownership on the staging directory " + > stagingArea + " is not as expected. " + > "It is owned by " + owner + ". The directory must " + > "be owned by the submitter " + currentUser + " or " + > "by " + realUser); > } > {noformat} > For file systems such as S3, which do not have permission concept, user can > never submit a job with staging area in S3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira