Difference between revisions of "Trove/ConfigurationParameters"
< Trove
(→Database Model) |
(→Database Model) |
||
| Line 27: | Line 27: | ||
|} | |} | ||
| − | * Denotes a primary key | + | {* Denotes a primary key} |
== API Details == | == API Details == | ||
Revision as of 20:17, 18 February 2014
Overview
Configuration Parameters need to be stored in the database and have a management api.
Database Model
| Name | Data Type | Length | Nullable | Details |
|---|---|---|---|---|
| id * | VARCHAR | 36 | False | unique id of the parameter |
| name | VARCHAR | 256 | False | name of the configuration parameter |
| datastore_version_id * | VARCHAR | 36 | False | datastore version id that the parameter is assigned to |
| restart_required | BOOLEAN | x | False | determines if the parameter requires the datastore to be restarted |
| max | INTEGER | x | True | max size of the parameter used for validation |
| min | INTEGER | x | True | min size of the parameter used for validation |
| data_type | VARCHAR | 256 | False | data type of the parameter |
| deleted | BOOLEAN | x | False | standard field to store if parameter is deleted |
| deleted_at | DATETIME | x | True | standard field to store when parameter is deleted |
{* Denotes a primary key}
API Details
| Verb | Resource | Description |
|---|---|---|
| POST | /mgmt/datastores/{datastore}/versions/{version}/parameters | Create a parameter for the given datastore version |
| PUT | /mgmt/datastores/{datastore}/versions/{version}/parameters/{key} | Modify a parameter for the given datastore version |
