hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13172) And an UnsupportedFeatureException for Filesystems to throw on unsupported operations
Date Wed, 18 May 2016 15:49:13 GMT

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

Chris Douglas commented on HADOOP-13172:
----------------------------------------

bq. What is the benefit to use a custom exception instead of a built in exception type?

+1 This seems very similar to HADOOP-12726. What's wrong with {{UnsupportedOperationException}}
in this case?

> And an UnsupportedFeatureException for Filesystems to throw on unsupported operations
> -------------------------------------------------------------------------------------
>
>                 Key: HADOOP-13172
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13172
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs
>    Affects Versions: 2.8.0
>            Reporter: Steve Loughran
>            Priority: Minor
>
> Filesystems which don't support things like append() tend to throw a simple IOE, which
makes it hard to distinguish "append didn't work for some IO problem" and "append isn't implemented".
> If we add a new exception, {{UnsupportedFeatureException}}, make it the strict failure
mode of such operations if not supported and patch all our filesystems to raise it, then at
least code has a straightforward check. Same for any other unimplemented feature



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

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message