stack table's uuid primary key wastes resources in other tables
Bug #1263787 reported by
Clint Byrum
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Triaged
|
Medium
|
Sirushti Murugesan |
Bug Description
The stack table should just have an integer primary key. Every event, for instance, has to have 36 bytes of UUID instead of a 4 byte integer pointer back to the stack. The same is true of every resource record and others as well.
The UUID should just be a secondary unique index.
Changed in heat: | |
milestone: | icehouse-2 → icehouse-3 |
Changed in heat: | |
milestone: | icehouse-3 → none |
Changed in heat: | |
assignee: | nobody → Visnusaran Murugan (visnusaran-murugan) |
Changed in heat: | |
assignee: | Visnusaran Murugan (visnusaran-murugan) → Unmesh Gurjar (unmesh-gurjar) |
Changed in heat: | |
assignee: | Unmesh Gurjar (unmesh-gurjar) → Visnusaran Murugan (visnusaran-murugan) |
Changed in heat: | |
assignee: | Visnusaran Murugan (visnusaran-murugan) → Unmesh Gurjar (unmesh-gurjar) |
Changed in heat: | |
assignee: | Unmesh Gurjar (unmesh-gurjar) → Visnusaran Murugan (visnusaran-murugan) |
Changed in heat: | |
milestone: | none → next |
importance: | High → Medium |
Changed in heat: | |
status: | In Progress → Triaged |
To post a comment you must log in.
Setting this to High priority