[HDFS-1012] documentLocation attribute in LdapEntry for HDFSProxy isn't specific to a cluster

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.20.1, 0.20.2, 0.21.0, 0.22.0
• Fix Version/s: 0.21.0
• Component/s: contrib/hdfsproxy
• Hadoop Flags: Reviewed

Release Note

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.

• Assignee: Srikanth Sundarrajan
• Reporter: Srikanth Sundarrajan
• Created: 01/Mar/10 07:58
• Updated: 24/Aug/10 20:52
• Resolved: 07/Apr/10 04:23

Description

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.

Issue Links

• requires: HDFS-481 Bug Fixes + HdfsProxy to use proxy user to impresonate the real user
• requires: HDFS-1010 HDFSProxy: Retrieve group information from UnixUserGroupInformation instead of LdapEntry