hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry for HDFSProxy isn't specific to a cluster
Date Tue, 06 Apr 2010 23:44:33 GMT

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

Tsz Wo (Nicholas), SZE updated HDFS-1012:
-----------------------------------------

    Fix Version/s:     (was: 0.20.1)
         Assignee: Srikanth Sundarrajan  (was: Ramesh Sekaran)

Here is my review comments:
- HDFS_PATH_PATTERN would not work if the port number is omitted.
- I suggest to store the namenode string in init(..).  Then, conf could become a local variable
in init(..)
- The current test seems not covering all of the cases.

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