hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry for HDFSProxy isn't specific to a cluster
Date Fri, 19 Mar 2010 12:31:27 GMT

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

>> Uploading patch for Ramesh 

It should be possible with this patch to fully qualify the documentLocation attorbute in ldap
to include the cluster name (fs.default.name). If the documentLocation in ldap is fully qualified,
the access is restricted by the proxy to that specific cluster, If the documentLocation is
not qualified, then access is not restricted to a cluster.

Backport patches: HDFS-1012-bp-y20.patch & HDFS-1012-bp-y20s.patch are not for commit.

> 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: Ramesh Sekaran
>             Fix For: 0.20.1, 0.22.0
>         Attachments: HDFS-1012-bp-y20.patch, HDFS-1012-bp-y20s.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.

View raw message