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 "eBugs (JIRA)" <ji...@apache.org> on 2019/05/07 12:43:00 UTC

[jira] [Commented] (HADOOP-16300) ebugs automated bug checker is reporting exception issues

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

eBugs commented on HADOOP-16300:
--------------------------------

Thanks for considering the bug reports! Sorry for making many of them at once (this is my first time to submit reports).

> ebugs automated bug checker is reporting exception issues
> ---------------------------------------------------------
>
>                 Key: HADOOP-16300
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16300
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 3.1.2
>            Reporter: eBugs
>            Priority: Major
>
> "ebugs-in-cloud-systems" is reporting issues related to exception handling
> Some of them may be be correct, some of them appear to have misunderstood issues.
> For reference
> * we aren't going to change the signature of public APIs, so new exception classes will not be added. anything which suggests that will be WONTFIX.
> * we probably aren't going to change code which throws unchecked exceptions to checked ones unless there is a good reason.
> * we can and do tighten the exceptions thrown in failures (e.g. replace an IOException with an InterruptedIOException. Patches welcome there, with tests.
> * making sure we don't lose the stack traces of inner causes would be nice too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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