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] [Updated] (JCLOUDS-187) ParseSwiftErrorFromHttpResponse.handleError should throw ContainerNotFoundException instead of KeyNotFoundException in all situations where container does not exist
Date Wed, 21 Jan 2015 21:58:36 GMT

     [ https://issues.apache.org/jira/browse/JCLOUDS-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Gaul updated JCLOUDS-187:
--------------------------------
    Labels: swift  (was: )

> ParseSwiftErrorFromHttpResponse.handleError should throw ContainerNotFoundException instead
of KeyNotFoundException in all situations where container does not exist
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-187
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-187
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-blobstore
>    Affects Versions: 1.6.1
>            Reporter: Andrew Gaul
>            Priority: Minor
>              Labels: swift
>
> ParseSwiftErrorFromHttpResponse.handleError always throws KeyNotFoundException for blob
operations reporting 404.  Could it parse the response from Swift and throw ContainerNotFoundException
instead?
> $ bin/jclouds-cli-1.6.1-incubating/bin/jclouds blobstore container-exists gaul-fakecontainer

> Container not found: gaul-fakecontainer not found: while checking existence
> $ bin/jclouds-cli-1.6.1-incubating/bin/jclouds blobstore write gaul-fakecontainer blob
input
> Blob not found: blob not found in container gaul-fakecontainer: <html><h1>Not
Found</h1><p>The resource could not be found.</p></html>



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

Mime
View raw message