[
https://issues.apache.org/jira/browse/MAPREDUCE-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13653141#comment-13653141
]
Steve Loughran commented on MAPREDUCE-5210:
-------------------------------------------
S3 is not a filesystem; it, Swift and others are blobstore, with no real notion
of directories, renames and deletes are non-atomic, time to retrieve data is
potentially both slow and nondeterministic.
Rather than try and make changes throughout future versions of Hadoop to
accomodate the use of S3 as a staging area, can I ask a question: Why do you
need to do this?
> 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
