Add metadata facility to account and container servers
Bug #616024 reported by
gholt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Object Storage (swift) |
Fix Released
|
Wishlist
|
gholt | ||
Bug Description
Feature Request:
Objects can currently have arbitrary metadata associated with them; it'd be nice to have the similar capabilities with accounts and containers. One difference would be that setting an account or container metadata item should have no effect on other metadata items. With objects, to set a new metadata item, you have to reset all existing metadata items or they are considered removed. This would be impractical with accounts and containers, so their metadata items should be versioned and replicated independently.
Related branches
lp:~gholt/swift/dbmetadata
- Mike Barton (community): Approve (redundant)
- Chuck Thier (community): Approve
-
Diff: 1219 lines (+735/-62)8 files modifiedswift/account/server.py (+52/-9)
swift/common/db.py (+130/-13)
swift/common/db_replicator.py (+22/-19)
swift/container/server.py (+46/-9)
test/unit/account/test_server.py (+88/-0)
test/unit/common/test_db.py (+292/-0)
test/unit/common/test_db_replicator.py (+13/-12)
test/unit/container/test_server.py (+92/-0)
| Changed in swift: | |
| status: | New → In Progress |
| Changed in swift: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Jay Pipes (jaypipes) wrote | #1 |
Revision history for this message
| gholt (gholt) wrote | #2 |
| Changed in swift: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Just an FYI, Greg, Launchpad's Blueprints are a better way to add feature requests (and track progress on tasks, especially related tasks). You can have subtasks and dependencies for blueprints, which makes tracking a finer grained status on the overall feature easier to visualize. For example, here's the "main" blueprint for Drizzle's replication feature set. You can visualize the relationship between all the subtasks by looking at the dependency graph:
https:/
All the different tasks in the dependency graph are clickable, allowing you to jump to subtask blueprints and their related branches easily.
Just a thought! :)
-jay