Actions
Feature #3542
closedmds: migration path for existing anchors, anchortables, etc.
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
Labels (FS):
Pull request ID:
Updated by Sage Weil over 11 years ago
- Translation missing: en.field_position deleted (
2) - Translation missing: en.field_position set to 18
Updated by Sage Weil over 11 years ago
- Translation missing: en.field_story_points set to 3
- Translation missing: en.field_position deleted (
18) - Translation missing: en.field_position set to 18
Updated by Sage Weil over 11 years ago
- Translation missing: en.field_position deleted (
26) - Translation missing: en.field_position set to 24
Updated by Greg Farnum over 11 years ago
What all does this encompass? Design? Implementation? Does it need to be an online switch or can it be an offline job?
Updated by Sage Weil over 11 years ago
Greg Farnum wrote:
What all does this encompass? Design? Implementation? Does it need to be an online switch or can it be an offline job?
All of the above.
A conversion that phases out the anchor table should probably be a separate feature. We might be able to freeze the table and use it only if we need to for existing metadata, and everything new gets backpointers. Especially since currently all the directories already have backpointers.
Updated by Greg Farnum over 11 years ago
- Translation missing: en.field_story_points deleted (
3) - Translation missing: en.field_position deleted (
19) - Translation missing: en.field_position set to 19
Updated by Greg Farnum over 11 years ago
- Translation missing: en.field_position deleted (
20) - Translation missing: en.field_position set to 28
Updated by Greg Farnum over 11 years ago
- Status changed from New to Duplicate
Actions