Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <33209950.1199488594042.JavaMail.jira@brutus>
Date: Fri, 4 Jan 2008 15:16:34 -0800 (PST)
From: "Raghu Angadi (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-2528) check permissions for job inputs
 and outputs
In-Reply-To: <9203511.1199477374276.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-2528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556111#action_12556111 ] 

Raghu Angadi commented on HADOOP-2528:
--------------------------------------

What if permissions checking is disabled (trunk currently allows it. it is in fact the default)? I don't think client alone can decide if a particular access is allowed, even if it is possible now. This looks similar to how DFS used to invoke '{{exits(file)}}' before opening a file.

Also this results in external commands to be run for LocalFileSystem for each file. Not that it is prohibitively expensive...

> 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.