Actions
Feature #418
closedrgw: object versioning
Status:
Duplicate
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
Not sure if this is accurate or not, but: http://doc.s3.amazonaws.com/betadesign/Versioning.html
- basic approach would be to clone objects when we complete a PUT, and read from the clone after the initial acl check.
- need to make accounting accurate so that we don't double-charge users
- need to clean out old clones, depending on the user retention policy
Updated by Sage Weil over 13 years ago
- Estimated time set to 8:00 h
- Source set to 3
Updated by Sage Weil about 13 years ago
- Translation missing: en.field_position deleted (
557) - Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 560
Updated by Sage Weil about 13 years ago
- Project changed from 4 to Ceph
- Category changed from radosgw to 22
Updated by Sage Weil almost 13 years ago
- Subject changed from support versioning to rgw: support object versioning
- Priority changed from Low to Normal
- Target version set to v0.33
Updated by Sage Weil almost 13 years ago
- Translation missing: en.field_position deleted (
670) - Translation missing: en.field_position set to 23
Updated by Sage Weil almost 13 years ago
- Translation missing: en.field_story_points deleted (
3) - Translation missing: en.field_position deleted (
31) - Translation missing: en.field_position set to 31
Updated by Sage Weil almost 13 years ago
- Subject changed from rgw: support object versioning to rgw: support object versioning ??
- Translation missing: en.field_position deleted (
31) - Translation missing: en.field_position set to 31
Updated by Sage Weil almost 13 years ago
- Translation missing: en.field_position deleted (
31) - Translation missing: en.field_position set to 35
Updated by Sage Weil almost 13 years ago
- Translation missing: en.field_position deleted (
35) - Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 771
Updated by Sage Weil over 12 years ago
- Target version changed from v0.33 to v0.34
Updated by Sage Weil over 12 years ago
- Subject changed from rgw: support object versioning ?? to rgw: atomic get
- Translation missing: en.field_position deleted (
774) - Translation missing: en.field_position set to 44
Updated by Sage Weil over 12 years ago
- Translation missing: en.field_position deleted (
44) - Translation missing: en.field_position set to 44
Updated by Sage Weil over 12 years ago
- Translation missing: en.field_position deleted (
50) - Translation missing: en.field_position set to 13
Updated by Sage Weil over 12 years ago
- Subject changed from rgw: atomic get to rgw: object versioning
Updated by Sage Weil over 12 years ago
- Target version changed from v0.34 to v0.35
- Translation missing: en.field_position deleted (
18) - Translation missing: en.field_position set to 1
Updated by Sage Weil over 12 years ago
- Translation missing: en.field_position deleted (
18) - Translation missing: en.field_position set to 25
Updated by Sage Weil over 12 years ago
- Translation missing: en.field_position deleted (
35) - Translation missing: en.field_position set to 1
- Translation missing: en.field_position changed from 1 to 824
Updated by Sage Weil over 12 years ago
- Target version changed from v0.35 to v0.36
- Translation missing: en.field_position deleted (
831) - Translation missing: en.field_position set to 2
Updated by Sage Weil over 12 years ago
- Target version deleted (
v0.36) - Translation missing: en.field_position deleted (
12) - Translation missing: en.field_position set to 20
Updated by Anonymous almost 12 years ago
- Project changed from Ceph to rgw
- Category deleted (
22)
Updated by Neil Levine about 11 years ago
- Translation missing: en.field_position deleted (
439) - Translation missing: en.field_position set to 3
Updated by Roald van Loon over 10 years ago
Versioning is quite a common feature nowadays, both in the S3 API as well as the Google Storage API. I really like to have it, is somebody working on this? If so, I'd like to join.
Updated by Yehuda Sadeh over 10 years ago
There's no one working on it right now AFAIK. I'd be more than happy to discuss this feature with you.
Actions