[
https://issues.apache.org/jira/browse/HADOOP-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556123#action_12556123
]
Doug Cutting commented on HADOOP-2528:
--------------------------------------
Let me be clear: permission checking of mapred inputs may not work very well
yet. But it should work in the 0.16 release. It looks like when
dfs.permissions=false that the returned file permissions are not all 777.
That's perhaps a bug. Either that, or the FileSystem#checkAccess() utility
method added by this patch should somehow check whether permissions are enabled.
It is better to begin to address such issues sooner than later in this release
cycle. If we advertise that file permissions are implemented in this release,
then we ought to attempt to make sure that they're usable, no? Checking
permissions while checking existence of inputs seems like a reasonable thing to
be able to do, should have no new significant performance impact, and causes us
to work some of these things out.
> check permissions for job inputs and outputs
> --------------------------------------------
>
> Key: HADOOP-2528
> URL: https://issues.apache.org/jira/browse/HADOOP-2528
> Project: Hadoop
> Issue Type: Improvement
> Components: mapred
> Reporter: Doug Cutting
> Fix For: 0.16.0
>
> Attachments: HADOOP-2528-0.patch
>
>
> On job submission, filesystem permissions should be checked to ensure that
> the input directory is readable and that the output directory is writable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
