You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hairong Kuang (JIRA)" <ji...@apache.org> on 2008/04/01 19:48:25 UTC

[jira] Issue Comment Edited: (HADOOP-2841) Dfs methods should not throw RemoteException

    [ https://issues.apache.org/jira/browse/HADOOP-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584218#action_12584218 ] 

hairong edited comment on HADOOP-2841 at 4/1/08 10:46 AM:
----------------------------------------------------------------

Can we unwrap the RemoteException at the ipc level?
When unwrapping RemoteException in DFSClient, I do not think we need to introduce a varaible "result" in every method.
Import "StringUtils" in FsShell is unneccessary.
In src/test/org/apache/hadoop/security/TestPermission.java, canXX methods only need to catch AccessControlException not IOException.


      was (Author: hairong):
    Can we unwrap the RemoteException at the ipc level?
When unwrapping RemoteException in DFSClient, I do not think we need to introduce a varaible "result" in every method.
Import "StringUtils" in FsShell is unneccessary.
Could you please also remove the unwrapping of RemoteException in src/test/org/apache/hadoop/security/TestPermission.java?

  
> Dfs methods should not throw RemoteException
> --------------------------------------------
>
>                 Key: HADOOP-2841
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2841
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>    Affects Versions: 0.16.0
>            Reporter: Hairong Kuang
>            Assignee: Konstantin Shvachko
>             Fix For: 0.17.0
>
>         Attachments: getNodeNPE.patch
>
>
> Dfs should unwrap the RemoteException and throw the real cause of the error to the user. This allows the user to find out the real cause without examining the remote exception. This also allows the user to use the dfs interface without aware of the implementation details (i.e. rpc).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.