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] [Resolved] (JCLOUDS-403) Add support for Swift object expiration
Date Wed, 11 Dec 2013 22:22:08 GMT

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

Andrew Gaul resolved JCLOUDS-403.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 1.7.0

> Add support for Swift object expiration
> ---------------------------------------
>
>                 Key: JCLOUDS-403
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-403
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-blobstore
>    Affects Versions: 1.7.0
>         Environment: Swift blobstore backend
>            Reporter: Craig Anderson
>            Assignee: Andrew Gaul
>              Labels: Expire, Header, Swift, X-Delete-At
>             Fix For: 1.7.0
>
>
> Andrew Gaul was kind enough to help me with a problem I was having expiring Swift objects,
which I explained in a stack overflow post here: http://stackoverflow.com/questions/20485579/expiring-swift-objects-with-jclouds
> I was able to test the patch he provided in the stack overflow response, and it addressed
my issue.  I am now able to PUT objects to Swift with an expiration date set that Swift understands.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message