Bug with Connection.update_table on global secondary index updates

[pior]

There is a bug in pynamodb.connection.Connection.update_table where updating a global secondary index fails with:

Invalid type for parameter GlobalSecondaryIndexUpdates[0].Update.ProvisionedThroughput.WriteCapacityUnits, value: None, type: <type 'NoneType'>, valid types: <type 'int'>, <type 'long'>
Invalid type for parameter GlobalSecondaryIndexUpdates[0].Update.ProvisionedThroughput.ReadCapacityUnits, value: None, type: <type 'NoneType'>, valid types: <type 'int'>, <type 'long'>

When comparing with the create_table() function, it's clear that the READ_CAPACITY_UNITS and WRITE_CAPACITY_UNITS keys are "converted" to camel case when they are already in camel case.

Here: https://github.com/jlafon/PynamoDB/blob/devel/pynamodb/connection/base.py#L435

[jlafon]

Just to be clear, @pior are you saying that the call to pythonic() is unnecessary?

[pior]

Since update_table() would typically be feed with the output of _get_indexes(), yes.

One element of _get_indexes():

{'index_name': 'by_account',
  'key_schema': [{'AttributeName': 'project_id', 'KeyType': 'HASH'},
   {'AttributeName': 'account_id', 'KeyType': 'RANGE'}],
  'projection': {'NonKeyAttributes': ['id',
    'push_platform',
    'push_endpoint_arn'],
   'ProjectionType': 'INCLUDE'},
  'provisioned_throughput': {'ReadCapacityUnits': 1, 'WriteCapacityUnits': 1}}