Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <141287109.1241186491304.JavaMail.jira@brutus>
Date: Fri, 1 May 2009 07:01:31 -0700 (PDT)
From: "Tom White (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Resolved: (HADOOP-5613) change S3Exception to checked
 exception
In-Reply-To: <1996578260.1238659813279.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-5613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom White resolved HADOOP-5613.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 0.21.0
         Assignee: Andrew Hitchcock
     Hadoop Flags: [Reviewed]

I've just committed this. Thanks Andrew!

> change S3Exception to checked exception
> ---------------------------------------
>
>                 Key: HADOOP-5613
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5613
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: fs/s3
>    Affects Versions: 0.18.3
>            Reporter: Andrew Hitchcock
>            Assignee: Andrew Hitchcock
>            Priority: Minor
>             Fix For: 0.21.0
>
>         Attachments: patch-ioexceptions.patch
>
>
> Currently the S3 filesystems can throw unchecked exceptions (S3Exception) which are not declared in the interface of FileSystem. These aren't caught by the various callers and can cause unpredictable behavior. IOExceptions are caught by most users of FileSystem since it is declared in the interface and hence is handled better.
> I propose we modify S3Exception to extend IOException.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.