ID should be biginteger in resource routing table
Bug #1647513 reported by
Chaoyi Huang
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Tricircle |
Fix Released
|
Undecided
|
Dongfeng Huang | ||
Bug Description
Currently the id in resource routing table is integer, the scope of integer is very limited, suggest to replace integer to biginteger
| Changed in tricircle: | |
| assignee: | nobody → Dongfeng Huang (southeast02) |
| Changed in tricircle: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to tricircle (master) | #1 |
| Changed in tricircle: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tricircle 3.0.0 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1533bb0f5194f3f
Author: Dongfeng Huang <email address hidden>
Date: Wed Dec 7 09:30:05 2016 +0800
ID should be biginteger in resource routing table
1. What is the problem?
Currently the id in resource routing table is integer, the scope of integer is
very limited, so it should be replaced with biginteger.
2. What is the solution to the problem?
Replacing the integer with biginteger will fix this problem. What's more,
API documentation should be updated at the same time.
3. What the features need to be implemented to the Tricircle to realize
the solution?
None.
Change-Id: I2be59348965fb2
Closes-Bug: #1647513