Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Message-ID: <335161188.1257876687968.JavaMail.jira@brutus>
Date: Tue, 10 Nov 2009 18:11:27 +0000 (UTC)
From: "Kan Zhang (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-6367) Move Access Token implementation
 from Common to HDFS
In-Reply-To: <1435633867.1257814896667.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-6367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12775972#action_12775972 ] 

Kan Zhang commented on HADOOP-6367:
-----------------------------------

> Does this mean there is no security if I run the JobTracker and TaskTracker on a non-HDFS based file system?
That depends on whether that non-HDFS based file system enforces any access control. It's unrelated to how HDFS does its access control. Access Token is a feature of HDFS and currently I don't see how other file systems could make use of it.

> Move Access Token implementation from Common to HDFS
> ----------------------------------------------------
>
>                 Key: HADOOP-6367
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6367
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Kan Zhang
>            Assignee: Kan Zhang
>
> Access Token is HDFS specific and should be part of HDFS code base. Also, rename AccessToken to BlockAccessToken (and AccessKey to BlockAccessKey) to be more precise.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.