You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/01/21 19:29:39 UTC

[jira] [Commented] (HADOOP-12726) Unsupported operations should throw UnsupportedOperationException

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

Steve Loughran commented on HADOOP-12726:
-----------------------------------------

in favour for all FS operations. In an ideal world, you'd even be able to tell in advance what was unsupported, but as it may depend on the specific FS instance, that's a tough one, especially for rawfs

> Unsupported operations should throw UnsupportedOperationException
> -----------------------------------------------------------------
>
>                 Key: HADOOP-12726
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12726
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 2.7.1
>            Reporter: Daniel Templeton
>            Assignee: Daniel Templeton
>
> In the {{FileSystem}} implementation classes, unsupported operations throw {{new IOException("Not supported")}}, which makes it needlessly difficult to distinguish an actual error from an unsupported operation.  They should instead throw {{new UnsupportedOperationException()}}.
> It's possible that this anti-idiom is used elsewhere in the code base.  This JIRA should include finding and cleaning up those instances as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)