Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-3642

add a HadoopIOException that can be thrown in any method that has IOException on its signature

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: 0.19.0
    • Fix Version/s: None
    • Component/s: util
    • Labels:
      None

      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.

        Attachments

        1. hadoop-io-exception.patch
          7 kB
          Steve Loughran
        2. hadoop-io-exception.patch
          7 kB
          Steve Loughran
        3. hadoop-io-exception.patch
          7 kB
          Steve Loughran

        Issue Links

          Activity

            People

            • Assignee:
              stevel@apache.org Steve Loughran
              Reporter:
              stevel@apache.org Steve Loughran

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment