mongodb stores traits inefficiently
Bug #1425584 reported by
gordon chung
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceilometer |
Won't Fix
|
Wishlist
|
Ankita Wagh | ||
Panko |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
currently mongodb stores each trait as:
{'trait_name': trait.name, 'trait_type': trait.dtype, 'trait_value': trait.value}
https:/
this is really inefficient as a trait is a key-value pair and could be stored as {trait.name: trait.value} but currently the mongodb stores the data exactly as the same way as data model. this can make updates to model difficult to fix in mongodb and it can dramatically increase the side of each event ie. instead of a trait being k:v, it's now 3 times the size)
description: | updated |
Changed in ceilometer: | |
assignee: | nobody → Ankita (ankita-wagh7) |
Changed in ceilometer: | |
status: | Triaged → Won't Fix |
Changed in panko: | |
importance: | Undecided → Wishlist |
status: | New → Triaged |
To post a comment you must log in.
thanks for looking at this. before you start you might want to ask in irc, mailing list, or meeting if others agree. the only scenario where the current model makes sense if we want to expand on what a trait is and add certain flags/tags to a trait... but i don't have a real use case to be honest which is why i personally think it can be fixed.