You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org> on 2010/03/01 09:00:06 UTC
[jira] Created: (HDFS-1012) documentLocation attribute in LdapEntry
for HDFSProxy isn't specific to a cluster
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
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.
[jira] Commented: (HDFS-1012) documentLocation attribute in
LdapEntry for HDFSProxy isn't specific to a cluster
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847345#action_12847345 ]
Hadoop QA commented on HDFS-1012:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12439270/HDFS-1012.patch
against trunk revision 925004.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 4 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output: http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/275/console
This message is automatically generated.
> 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.
[jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry
for HDFSProxy isn't specific to a cluster
Posted by "Ramesh Sekaran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramesh Sekaran updated HDFS-1012:
---------------------------------
Fix Version/s: 0.20.1
0.22.0
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.
Status: Patch Available (was: In Progress)
> 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.2, 0.20.1, 0.21.0, 0.22.0
> Reporter: Srikanth Sundarrajan
> Assignee: Ramesh Sekaran
> Fix For: 0.22.0, 0.20.1
>
>
> 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.
[jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry
for HDFSProxy isn't specific to a cluster
Posted by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org>.
[ 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-bp-y20.patch
Updated backport patch with the review comments
> 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-y20.patch, HDFS-1012-bp-y20s.patch, HDFS-1012.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.
[jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry
for HDFSProxy isn't specific to a cluster
Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz Wo (Nicholas), SZE updated HDFS-1012:
-----------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I have committed this. Thanks, Srikanth!
> 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, 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.
[jira] Work started: (HDFS-1012) documentLocation attribute in
LdapEntry for HDFSProxy isn't specific to a cluster
Posted by "Ramesh Sekaran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on HDFS-1012 started by Ramesh Sekaran.
> 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
>
> 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.
[jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry
for HDFSProxy isn't specific to a cluster
Posted by "Ramesh Sekaran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramesh Sekaran updated HDFS-1012:
---------------------------------
Status: Open (was: Patch Available)
Unable to upload patch. Will get the patch uploaded by others
> 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.2, 0.20.1, 0.21.0, 0.22.0
> Reporter: Srikanth Sundarrajan
> Assignee: Ramesh Sekaran
> Fix For: 0.22.0, 0.20.1
>
>
> 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.
[jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry
for HDFSProxy isn't specific to a cluster
Posted by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org>.
[ 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-bp-y20.patch
Revised backport patch for yhadoop20
> 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-y20.patch, HDFS-1012-bp-y20.patch, HDFS-1012-bp-y20s.patch, HDFS-1012.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.
[jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry
for HDFSProxy isn't specific to a cluster
Posted by "Ramesh Sekaran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramesh Sekaran updated HDFS-1012:
---------------------------------
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 accessible on all clusters.
was:
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.
[jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry
for HDFSProxy isn't specific to a cluster
Posted by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org>.
[ 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
HDFS-1012-bp-y20s.patch
HDFS-1012-bp-y20.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.
[jira] Assigned: (HDFS-1012) documentLocation attribute in
LdapEntry for HDFSProxy isn't specific to a cluster
Posted by "Ramesh Sekaran (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ramesh Sekaran reassigned HDFS-1012:
------------------------------------
Assignee: Ramesh Sekaran
> 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
>
> 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.
[jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry
for HDFSProxy isn't specific to a cluster
Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry
for HDFSProxy isn't specific to a cluster
Posted by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org>.
[ 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
{quote}
* 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.
{quote}
Nicholas, Thanks for your review comments. Revised patch uploaded with the following changes
1. HDFS_PATH_PATTERN replaced from ^hdfs://([\\w\\-]+(\\.)?)+:\\d+ to (^hdfs://([\\w\\-]+(\\.)?)+:\\d+|^hdfs://([\\w\\-]+(\\.)?)+) to support cases with no port #
2. conf.get("fs.default.name") is retrieved once in init and namenode url stored for future reference and access. This doesn't change within the filter while webapp context is running
3. Three additional test cases have been added
* Case for allowing a request with a valid unqualified documentLocation (path)
* Case for allowing a request with a valid qualified documentLocation
* Case for rejecting request where documentLocation doesn't contain a valid path for the cluster in question
------ 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 5 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.
[cactus] Running org.apache.hadoop.hdfsproxy.TestAuthorizationFilter
[cactus] Tomcat 5.x started on port [30300]
[cactus] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.972 sec
[cactus] Running org.apache.hadoop.hdfsproxy.TestLdapIpDirFilter
[cactus] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.789 sec
[cactus] Running org.apache.hadoop.hdfsproxy.TestProxyFilter
[cactus] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.867 sec
[cactus] Running org.apache.hadoop.hdfsproxy.TestProxyForwardServlet
[cactus] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.508 sec
[cactus] Running org.apache.hadoop.hdfsproxy.TestProxyUtil
[cactus] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.84 sec
[cactus] Tomcat 5.x is stopping...
[cactus] Tomcat 5.x is stopped
test:
BUILD SUCCESSFUL
Total time: 4 minutes 8 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: Srikanth Sundarrajan
> Fix For: 0.22.0
>
> Attachments: HDFS-1012-bp-y20.patch, HDFS-1012-bp-y20s.patch, HDFS-1012.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.
[jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry
for HDFSProxy isn't specific to a cluster
Posted by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Srikanth Sundarrajan updated HDFS-1012:
---------------------------------------
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.
was:
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 accessible on all clusters.
Status: Patch Available (was: Open)
Patches for HDFS-481 & HDFS-1010 need to be applied before this patch
> 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.2, 0.20.1, 0.21.0, 0.22.0
> Reporter: Srikanth Sundarrajan
> Assignee: Ramesh Sekaran
> Fix For: 0.22.0, 0.20.1
>
> 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.
[jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry
for HDFSProxy isn't specific to a cluster
Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz Wo (Nicholas), SZE updated HDFS-1012:
-----------------------------------------
Hadoop Flags: [Reviewed]
+1 the new patch is perfect!
> 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, 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.
[jira] Commented: (HDFS-1012) documentLocation attribute in
LdapEntry for HDFSProxy isn't specific to a cluster
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HDFS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854350#action_12854350 ]
Hudson commented on HDFS-1012:
------------------------------
Integrated in Hadoop-Hdfs-trunk-Commit #234 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/234/])
. hdfsproxy: Support for fully qualified HDFS path in addition to simple unqualified path. Contributed by Srikanth Sundarrajan
> 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, 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.
[jira] Commented: (HDFS-1012) documentLocation attribute in
LdapEntry for HDFSProxy isn't specific to a cluster
Posted by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HDFS-1012) documentLocation attribute in
LdapEntry for HDFSProxy isn't specific to a cluster
Posted by "Ramesh Sekaran (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HDFS-1012) documentLocation attribute in LdapEntry
for HDFSProxy isn't specific to a cluster
Posted by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org>.
[ 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-bp-y20s.patch
Revised backport patch for yhadoop20s in sync with trunk patch revisions
> 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-y20.patch, HDFS-1012-bp-y20.patch, HDFS-1012-bp-y20s.patch, HDFS-1012-bp-y20s.patch, HDFS-1012.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.