[
https://issues.apache.org/jira/browse/HADOOP-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590657#action_12590657
]
Tsz Wo (Nicholas), SZE commented on HADOOP-3273:
------------------------------------------------
The name change is not necessary since there is no ambiguity (otherwise it
won't compile).
We have this kind of name collision between hadoop and java, e.g.
java.rmi.RemoteException and org.apache.hadoop.ipc.RemoteException.
> Name collision for AccessControlException.
> ------------------------------------------
>
> Key: HADOOP-3273
> URL: https://issues.apache.org/jira/browse/HADOOP-3273
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.16.0
> Reporter: Konstantin Shvachko
> Fix For: 0.18.0
>
>
> There is a name collision in
> org.apache.hadoop.fs.permission.AccessControlException and
> java.security.AccessControlException.
> Since java.security.AccessControlException is not an IOException we cannot
> throw it directly as we do with FileNotFoundException.
> Therefore, the only choice is to rename the hadoop AccessControlException to
> e.g., PermissionException (or AccessDeniedException).
> To provide compatibility we can inherit PermissionException from
> AccessControlException, and deprecate the latter.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
