[
https://issues.apache.org/jira/browse/HADOOP-9597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666493#comment-13666493
]
Jerry He commented on HADOOP-9597:
----------------------------------
Hi, Suresh
Thanks for you comment.
But isn't this a problem? FileSystem interface is such an important interface.
We have a proprietary implementation of FileSystem that does not throws
FileNotFoundException.
It causes a problem for HBase, which expects FileNotFoundException in one
particular case.
There could be other implementations out there.
Java FileInputStream specifically throws FileNotFoundException, which is
commonly used.
We need to be clear, of course unless we intend to be ambiguous in this case.
> FileSystem open() API is not clear if FileNotFoundException is throw when the
> path does not exist
> -------------------------------------------------------------------------------------------------
>
> Key: HADOOP-9597
> URL: https://issues.apache.org/jira/browse/HADOOP-9597
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation, fs
> Affects Versions: 2.0.4-alpha
> Reporter: Jerry He
> Priority: Minor
> Fix For: 2.0.4.1-alpha
>
>
> The current FileSystem open() method throws a generic IOException in its API
> specification.
> Some FileSystem implementations (DFS, RawLocalFileSystem ...) throws more
> specific FileNotFoundException if the path does not exist. Some throws
> IOException only (FTPFileSystem, HftpFileSystem ...).
> If we have a new FileSystem implementation, what should we follow exactly for
> open()?
> What should the application expect in this case.
>
--
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
