Bug #4941
Save plankton properties in separate entries in the pithos backend
| Status: | Closed | Start date: | 01/16/2014 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Sofia Papagiannaki | % Done: | 0% |
|
| Category: | Plankton | Spent time: | - | |
| Target version: | 0.15 |
Description
The entry length is too limited for saving all the properties in a json string and results in the following error:
DataError: (DataError) value too long for type character varying(256)
'UPDATE attributes SET value=%(value)s WHERE attributes.serial = %(serial_1)s AND attributes.domain = %(domain_1)s AND attributes.key = %(key_1)s' {'domain_1': 'plankton', 'serial_1': 1698304, 'key_1': 'plankton:properties', 'value': '{"partition_table": "msdos", "osfamily": "linux", "users": "root openfiler ofguest", "root_partition": "2", "exclude_assign_hostname": "yes", "exclude_task_assignhostname": "yes", "exclude_assignhostname": "yes", "os": "linux", "swap": "3:1028", "description": "Openfiler 2.99"}'}
Moreover, there should be also a migration of the existing plankton properties.
Associated revisions
plankton: Save properties in separate entries in the backend
Refs: #4941
History
#1 Updated by Sofia Papagiannaki over 9 years ago
Commit for the pithos db migration:
1ec057163c3937b12a71c820cc6ce55cd282c032
#2 Updated by Sofia Papagiannaki over 9 years ago
Plankton should fail with 400 (BadRequest) if a property key or value is too long to fit to the respective database field.
#3 Updated by Sofia Papagiannaki over 9 years ago
- Status changed from Assigned to Closed
Replaced by the following alternative implementation:
d58ea30ac4f24f2638eff22b31c20c991975237b