[
https://issues.apache.org/jira/browse/HDFS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854144#action_12854144
]
Srikanth Sundarrajan commented on HDFS-1012:
--------------------------------------------
Note: HDFS-481, HDFS-1009 and HDFS-1010 will need to be committed before this
patch can be applied
Output from test-patch & test-contrib
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 4 new or
modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning
messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number
of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs
warnings.
[exec]
[exec] +1 release audit. The applied patch does not increase the
total number of release audit warnings.
test:
BUILD SUCCESSFUL
Total time: 4 minutes 32 seconds
> 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.
