[
https://issues.apache.org/jira/browse/HADOOP-2652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561445#action_12561445 ]
Hairong Kuang commented on HADOOP-2652:
---------------------------------------
1. HftpFileSystem.initialize should throw a LoginException when login failed. Otherwise, A NullPointerException might be thrown when a URL is constructed.
2. ListPathsServlet and FileDataServlet talks to namenode through RPC not by direct method call. Shall we concern about the performance?
3. ListPathsServlet.writeInfo should also write a path's permission-related info back to the client.
4, For secondary namenode communication, I think it is better to check the user in getFileServer and getInfoServer. This means that these two methods can not be static.
5. Can we also enforce user checking for NamenodeProtocol?
6. The patch passes the user info to StreamFile servlets but the user info is not used. Since currently dfs does not check user authorization for client to datanode communications, I feel it is better to do it later on.
> Fix permission issues for HftpFileSystem
> ----------------------------------------
>
> Key: HADOOP-2652
> URL:
https://issues.apache.org/jira/browse/HADOOP-2652> Project: Hadoop
> Issue Type: Bug
> Components: dfs
> Reporter: Tsz Wo (Nicholas), SZE
> Assignee: Tsz Wo (Nicholas), SZE
> Priority: Blocker
> Attachments: 2652_20080117.patch, 2652_20080117b.patch
>
>
> Similar to HADOOP-2614, HftpFileSystem requires UserGroupInformation to access NameNode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
