Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <1182050607.40901270641574007.JavaMail.jira@brutus.apache.org>
Date: Wed, 7 Apr 2010 11:59:34 +0000 (UTC)
From: "Srikanth Sundarrajan (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry
 for HDFSProxy isn't specific to a cluster
In-Reply-To: <297399032.28531267430406172.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HDFS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Srikanth Sundarrajan updated HDFS-1012:
---------------------------------------

    Attachment: HDFS-1012-bp-y20.patch

Revised backport patch for yhadoop20

> documentLocation attribute in LdapEntry for HDFSProxy isn't specific to a cluster
> ---------------------------------------------------------------------------------
>
>                 Key: HDFS-1012
>                 URL: https://issues.apache.org/jira/browse/HDFS-1012
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: contrib/hdfsproxy
>    Affects Versions: 0.20.1, 0.20.2, 0.21.0, 0.22.0
>            Reporter: Srikanth Sundarrajan
>            Assignee: Srikanth Sundarrajan
>             Fix For: 0.22.0
>
>         Attachments: HDFS-1012-bp-y20.patch, HDFS-1012-bp-y20.patch, HDFS-1012-bp-y20.patch, HDFS-1012-bp-y20s.patch, HDFS-1012.patch, HDFS-1012.patch
>
>
> List of allowed document locations accessible through HDFSProxy isn't specific to a cluster. LDAP entries can include the name of the cluster to which the path belongs to have better control on which clusters/paths are accessible through HDFSProxy by the user.

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