UpdateTable

Last Updated: Oct 11, 2016

UpdateTable

Action:

Updates the reserved read or write throughput settings of the specified table. The new settings will take effect within one minute of a successful update.

Request Structure:

  1. message UpdateTableRequest {
  2. required string table_name = 1;
  3. required ReservedThroughput reserved_throughput = 2;
  4. }

table_name:

  • Type: string

  • Required Parameter: Yes

  • The name of the table for which to change the reserved read/write throughput settings.

reserved_throughput:

  • Type: ProvisionedThroughput

  • Required Parameter: Yes

  • The reserved read/write throughput settings for the table to change. These settings will take effect in one minute.

  • You may update either the table’s reserved read or write throughput settings, or both.

  • In capacity_unit, read and write should at least have a non-null value. Otherwise, the request will fail and return an error.

Response Message Structure:

  1. message UpdateTableResponse {
  2. required ReservedThroughputDetails reserved_throughput_details = 1;
  3. }

capacity_unit_details:

  • Type: ProvisionedThroughputDetails

  • After the update, besides containing the current reserved read/write throughput settings, the table’s reserved read/write throughput settings information will also contain the time these settings were last updated and the number of times they have been lowered for the current date.

Tips

  • The minimum time interval between adjustments to a table’s reserved read/write throughput is 10 minutes. If the current UpdateTable operation comes less than 10 minutes after the last one, it will be rejected.

  • Within a single calendar day (from 00:00:00 to 00:00:00 the next day in UTC time), each table’s reserved read/write throughput may be raised an unlimited number of times, but lowered no more than 4 times. Lowering either the reserved read throughput or write throughput is viewed as lowering the reserved read/write throughput.

Request Example:

  1. UpdateTableRequest {
  2. table_name: "consume_history"
  3. capacity_unit {
  4. read: 10
  5. write: 150
  6. }
  7. }

Response Example:

  1. UpdateTableResponse {
  2. capacity_unit_details {
  3. capacity_unit {
  4. read: 10
  5. write: 150
  6. }
  7. last_increase_time: 1407507306
  8. last_decrease_time: 1407507306
  9. number_of_decreases_today: 2
  10. }
  11. }
Thank you! We've received your feedback.