Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Increasing to a minimum provisioned throughput value doesn't take into account the current table's throughput #45
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.