jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Gaul (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-650) getBlob for non-existent containers does not throw a ContainerNotFoundException
Date Wed, 06 Aug 2014 22:57:11 GMT

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

Andrew Gaul commented on JCLOUDS-650:
-------------------------------------

I think it's worth stepping back and asking what the desired behavior is, then aligning the
implementations with that.  Can we reliably distinguish between ContainerNotFound and KeyNotFound
for all the providers?

> getBlob for non-existent containers does not throw a ContainerNotFoundException
> -------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-650
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-650
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 1.7.3
>            Reporter: Shri Javadekar
>            Assignee: Jeremy Daggett
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> As per the documentation[1], the BlobStore object should throw a ContainerNotFoundException
if the container does not exist when the getBlob API is invoked. However, I see that the call
to getBlob silently succeeds when the container doesn't exist. I tested this against aws-s3,
swift and cloudfiles-us.
> [1] http://jclouds.apache.org/reference/javadoc/1.7.x/org/jclouds/blobstore/BlobStore.html#getBlob(java.lang.String,
java.lang.String)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message