Actions
Feature #2362
openrados: support omap (leveldb) and locator key in import/export
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
Observed by Henry C Chang: http://marc.info/?l=ceph-devel&m=133575684918035&w=2
Also see #1069 for similar ticket on xattrs.
We'll need to be careful to handle collisions with user data, but we should be able to:
1) Store the locator as an xattr
2) Store the omap data in a specially-named separate file, which is linked to the "parent" file via an xattr on both files.
Updated by Sage Weil almost 12 years ago
- Translation missing: en.field_position set to 7
Updated by Sage Weil almost 12 years ago
- Translation missing: en.field_position deleted (
11) - Translation missing: en.field_position set to 10
Updated by Sage Weil almost 12 years ago
- Subject changed from rados: support omap (leveldb) in import/export to rados: support omap (leveldb), locator key in import/export
- Translation missing: en.field_position deleted (
11) - Translation missing: en.field_position set to 11
Updated by Greg Farnum almost 12 years ago
- Subject changed from rados: support omap (leveldb), locator key in import/export to rados: support omap (leveldb) and locator key in import/export
- Description updated (diff)
Updated by Sage Weil almost 12 years ago
- Translation missing: en.field_position deleted (
25) - Translation missing: en.field_position set to 6
Updated by Sage Weil almost 12 years ago
- Translation missing: en.field_position deleted (
17) - Translation missing: en.field_position set to 13
Updated by Sage Weil almost 12 years ago
- Translation missing: en.field_position deleted (
42) - Translation missing: en.field_position set to 1
Actions