You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/12/11 23:22:07 UTC
[jira] [Commented] (JCLOUDS-403) Add support for Swift object
expiration
[ https://issues.apache.org/jira/browse/JCLOUDS-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845782#comment-13845782 ]
ASF subversion and git services commented on JCLOUDS-403:
---------------------------------------------------------
Commit 3321506c849a29b79499a820bc9c895b1c657c66 in branch refs/heads/master from [~gaul]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=3321506 ]
JCLOUDS-403. Add support for Swift object expiry
> 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)