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 "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2013/11/01 00:32:17 UTC

[jira] [Commented] (HADOOP-9623) Update jets3t dependency to 0.9.0

    [ https://issues.apache.org/jira/browse/HADOOP-9623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13810860#comment-13810860 ] 

Colin Patrick McCabe commented on HADOOP-9623:
----------------------------------------------

Looks straightforward in general.

{code}
+    } catch (ServiceException e) {
+      return null;
     }
   }
 
@@ -194,6 +197,8 @@ private InputStream get(String key, long byteRangeStart) throws IOException {
         throw (IOException) e.getCause();
       }
       throw new S3Exception(e);
+    } catch (ServiceException e) {
+      return null;
     }
   }
 {code}

Why are these exceptions ignored?  Should they be logged?  Or could we at least check the exception text before doing this?

> Update jets3t dependency to  0.9.0 
> -----------------------------------
>
>                 Key: HADOOP-9623
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9623
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: fs/s3
>    Affects Versions: 3.0.0, 2.1.0-beta, 2.2.0
>            Reporter: Timothy St. Clair
>            Assignee: Amandeep Khurana
>              Labels: maven
>         Attachments: HADOOP-9623.patch, HADOOP-9623.patch, HADOOP-9623_2.patch
>
>
> Current version referenced in pom is 0.6.1 (Aug 2008), updating to 0.9.0 enables mvn-rpmbuild to build against system dependencies. http://jets3t.s3.amazonaws.com/RELEASE_NOTES.html



--
This message was sent by Atlassian JIRA
(v6.1#6144)