Creating a configuration with a large parameter value causes HTTP 422

MySQL has a variable called myisam_sort_buffer_size. Calling /datastores/<etc>/parameters/myisam_sort_buffer_size shows its max value as 18446744073709547520. Creating or updating a configuration with this value causes Trove to return an HTTP 422 error. Example data: '{"configuration": {"name":"configuration_integer", "values": {"myisam_sort_buffer_size": 18446744073709547520}}}'

Steps to Reproduce

1. Make a call to <api>/datastores/mysql/versions/<version>/parameters/myisam_sort_buffer_size.
This returns the parameter details of myisam_sort_buffer_size.
{"max": 18446744073709547520, "min": 4, "type": "integer", "name": "myisam_sort_buffer_size", "restart_required": false}

2. Attempt to create a configuration with myisam_sort_buffer_size's max value. This returns HTTP 422 Unprocessable Entity
<api>/configurations/<configuration_id> POST, Tenant, AuthToken, Data = '{"configuration": {"name":"configuration_integer", "values": {"myisam_sort_buffer_size": 18446744073709547520}}}'

HTTP 422 Unprocessable Entity
{"unprocessableEntity": {"message": "The value provided for the configuration parameter myisam_sort_buffer_size is not of type integer.", "code": 422}}

3. I suspect the value is being limited by python's max_int value (9223372036854775807).

----
9223372036854775808 does not work:
<api>/configurations POST, Tenant, AuthToken, Data = '{"configuration": {"name":"configuration_integer", "values": {"myisam_sort_buffer_size": 9223372036854775808}}}'

HTTP 422 Unprocessable Entity
{"unprocessableEntity": {"message": "The value provided for the configuration parameter myisam_sort_buffer_size is not of type integer.", "code": 422}}

----
9223372036854775807 does work:
<api>/configurations POST, Tenant, AuthToken, Data = '{"configuration": {"name":"configuration_integer", "values": {"myisam_sort_buffer_size": 9223372036854775807}}}'

HTTP 200 OK
{"configuration": {"description": null, "values": {"myisam_sort_buffer_size": 9223372036854775807}, "id": <id>, "datastore_version_id": <datastore_id>, "name": "configuration_integer"}}

----
A GET on this configuration works:
<api>/configurations/<configuration_id> GET, Tenant, AuthToken

HTTP 200 OK
{"configuration": {"description": null, "values": {"myisam_sort_buffer_size": 9223372036854775807}, "id": <id>, "datastore_version_id": <datastore_id>, "name": "configuration_integer"}}