[
https://issues.apache.org/jira/browse/HADOOP-9094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507383#comment-13507383
]
Suresh Srinivas commented on HADOOP-9094:
-----------------------------------------
bq. Maybe I'm confused about what option #2
Sorry my comment was not very clear. Here is another attempt to make it clear:
* Move formatting exception message into a static utility method
* Option 1: Subclass the well known java/hadoop exception
** PathNotFoundException subclasses FileNotFoundException. It formats the
exception message using the utility.
** PathAccessException - rename to PathAccessControlException. Make it a
subclass of AccessControlException. It also formats the exception message using
the utility.
* Option 2: Just use the well known java/hadoop exception
** Remove PathNotFoundException. Use FileNotFoundException. Retain the format
of the exception message.
** Remove PathAccessException. Use AccessControlException. Retain the format of
the exception message.
I am leaning towards Option 2.
> Add interface audience and stability annotation to PathExceptions
> -----------------------------------------------------------------
>
> Key: HADOOP-9094
> URL: https://issues.apache.org/jira/browse/HADOOP-9094
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 3.0.0
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
>
> HADOOP-9093 moved path related exceptions to o.a.h.fs. This jira tracks
> adding interface audience and stability to notation to those exceptions. It
> also tracks the comment from HADOOP-9093:
> bq. I propose using FileNotFoundException instead of PathNotFoundException as
> it is already extensively used. Similarly use AccessControlException instead
> of PathAccessException. If folks agree, I will make that change in the next
> patch. Alternatively we could at least make these exceptions subclasses of
> the exception that I am proposing replacing them with.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
