Say for instance I have a table with a write throughput of 2, and in my configuration, that table's minimum write throughput is set to 5. When attempting to increase to that minimum write throughput, amazon will throw an error, because you can only increase table's throughput up to twice the amount of the current throughput. Might I suggest something along the lines of:
return min( get_table_option(table_name, 'min_provisioned_reads'), (current_provisioning * 2) )
return min( get_table_option(table_name, 'min_provisioned_writes'), (current_provisioning * 2) )
When returning a minimum provisioned read or write value so that the table can at least get closer to it's minimum provisioned value.
I suppose this is an edge case, but I'd rather give you the option to ignore it instead of the issue never being heard.
Hi, @alxmrtn! Thanks for the bug report. I am on a trip to Berlin at the moment. Will have a look at this during the weekend!
Addressed #45 with a minor fix
I have addressed this in a fix now. The fix has not yet been tested, but it is available in the hotfix/1.3.3 branch. Will release 1.3.3 during the weekend!
This has now been fixed and shipped with version 1.3.3. Thanks again for the feedback @alxmrtn