You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/06/15 15:23:00 UTC
[jira] [Commented] (HADOOP-14510) Use error code detail in AWS
server responses for finer grained exceptions
[ https://issues.apache.org/jira/browse/HADOOP-14510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050613#comment-16050613 ]
Steve Loughran commented on HADOOP-14510:
-----------------------------------------
Also, HADOOP-14326 wants a 405 "object lost" error
> Use error code detail in AWS server responses for finer grained exceptions
> --------------------------------------------------------------------------
>
> Key: HADOOP-14510
> URL: https://issues.apache.org/jira/browse/HADOOP-14510
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.8.1
> Reporter: Steve Loughran
>
> {{S3Utils.translateException()}} maps HTTP status code to exceptions. We aren't looking at the body of the reponses though, except when handling a 301 redirect.
> We should use the exit code to fine tune responses, especially 400 & 401/403.
> Right now I'm not sure we are even getting that error code into the text.
> see: http://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org