[HADOOP-3642] add a HadoopIOException that can be thrown in any method that has IOException on its signature

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 0.19.0
• Component/s: util
• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 25/Jun/08 11:09
• Updated: 02/May/13 02:29
• Resolved: 27/Jun/08 14:06

Description

I find myself having to throw IOExceptions a lot, and create new ones -but the classes signature varies from java1.5 to 1.6, and the base IOException is fairly meaningless. If Hadoop added a HadoopIOException, it could be thrown whenever hadoop's own code needed to create new IOExceptions, and possibly be differentiated in the catch() logic.

The biggest disadvantage of doing this is that as IOException is built into the JVM, you can be sure that the far end will be able to deserialize it under RMI, without having the rest of hadoop on the classpath. This is not a feature of hadoop, so should not be an issue. For those of us who do use RMI, well, we'd better get our classpaths right.

Issue Links

• is depended upon by: HDFS-326 Add a lifecycle interface for Hadoop components: namenodes, job clients, etc.