You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Íñigo Goiri (JIRA)" <ji...@apache.org> on 2019/06/06 19:01:00 UTC
[jira] [Updated] (HDFS-14486) The exception classes in some throw
statements do not accurately describe why they are thrown
[ https://issues.apache.org/jira/browse/HDFS-14486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Íñigo Goiri updated HDFS-14486:
-------------------------------
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Thanks [~ebugs-in-cloud-systems] for reporting and [~ayushtkn] for the fix.
Committed to trunk.
> The exception classes in some throw statements do not accurately describe why they are thrown
> ---------------------------------------------------------------------------------------------
>
> Key: HDFS-14486
> URL: https://issues.apache.org/jira/browse/HDFS-14486
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: eBugs
> Assignee: Ayush Saxena
> Priority: Minor
> Attachments: HDFS-14486-01.patch, HDFS-14486-02.patch, HDFS-14486-03.patch, HDFS-14486-04.patch
>
>
> Dear HDFS developers, we are developing a tool to detect exception-related bugs in Java. Our prototype has spotted a few {{throw}} statements whose exception class does not accurately describe why they are thrown. This can be dangerous since it makes correctly handling them challenging. For example, in an old bug, HDFS-8224, throwing a general {{IOException}} makes it difficult to perform data recovery specifically when a metadata file is corrupted.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org