hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramesh Sekaran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (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:comment-tabpanel&focusedCommentId=12847342#action_12847342
] 

Ramesh Sekaran commented on HDFS-1012:
--------------------------------------

Support for fully qualified HDFS path in addition to simple unqualified path.
The qualified path indicates that the path is accessible on the specific HDFS. Non qualified
path is qualified in all clusters.

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


Mime
View raw message