[
https://issues.apache.org/jira/browse/JCLOUDS-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088098#comment-14088098
]
Jeremy Daggett commented on JCLOUDS-650:
----------------------------------------
The Swift documentation states that a {{404 Not Found}} it returned when
requesting an
[Object|http://docs.openstack.org/api/openstack-object-storage/1.0/content/GET_getObject__v1__account___container___object__storage_object_services.html]
or
[Container|http://docs.openstack.org/api/openstack-object-storage/1.0/content/GET_showContainerDetails__v1__account___container__storage_container_services.html]
that does not exist.
>From what I see in the code, this behavior is consistent in both {{swift}} and
>{{openstack-swift}} and they return null in both cases. I am not sure this is
>a bug in the code, but rather in the docs.
> 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)
