Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 11 May 2016 10:58:12 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: <JIRA.12967367.1462964255000.164342.1462964292897@Atlassian.JIRA>
In-Reply-To: <JIRA.12967367.1462964255000@Atlassian.JIRA>
References: <JIRA.12967367.1462964255000@Atlassian.JIRA> <JIRA.12967367.1462964255026@arcas>
Subject: [jira] [Created] (HADOOP-13130) s3a failures can surface as RTEs,
 not IOEs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 11 May 2016 10:58:20 -0000

Steve Loughran created HADOOP-13130:
---------------------------------------

             Summary: s3a failures can surface as RTEs, not IOEs
                 Key: HADOOP-13130
                 URL: https://issues.apache.org/jira/browse/HADOOP-13130
             Project: Hadoop Common
          Issue Type: Bug
          Components: fs/s3
    Affects Versions: 2.7.2
            Reporter: Steve Loughran


S3A failures happening in the AWS library surface as {{AmazonClientExceptio=
n}} derivatives, rather than IOEs. As the amazon exceptions are runtime exc=
eptions, any code which catches IOEs for error handling breaks.

The fix will be to catch and wrap. The hard thing will be to wrap it with m=
eaningful exceptions rather than a generic IOE. Furthermore, if anyone has =
been catching AWS exceptions, they are going to be disappointed. That means=
 that fixing this situation could be considered "incompatible" =E2=80=94but=
 only for code which contains assumptions about the underlying FS and the e=
xceptions they raise.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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