[
https://issues.apache.org/jira/browse/HADOOP-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556103#action_12556103
]
Doug Cutting commented on HADOOP-2528:
--------------------------------------
> Is it to fail early or is there some other fundamental requirement?
Just to fail early, like most other checks of inputs and outputs.
> I think weather a given user can write to a file or directory is pretty
> filesystem dependent
Right. That's why each filesystem can implement permissions. The default
implementation permits everything, so these tests will succeed unless a
filesystem has implemented permissions.
Also, we've discussed other places recently (e.g., trash) where user-level code
will do permission checking. This is an opportunity to push on that, to see if
the APIs are usable, etc. It should be easy to add permission checking code to
applications, and it shouldn't break them. The sooner we get some such code
into the system the sooner we'll beat out problems in the permission
implementation and APIs. Permissions are probably the biggest new feature in
0.16, so now's the time to make sure they're usable.
> 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.
