update_global_table_settings
async
¶
update_global_table_settings(
global_table_name: TableName,
*,
config_overrides: Optional[AsyncDynamoDBClientConfig] = None,
global_table_billing_mode: Optional[BillingMode] = None,
global_table_provisioned_write_capacity_units: Optional[PositiveLongObject] = None,
global_table_provisioned_write_capacity_auto_scaling_settings_update: Optional[
AutoScalingSettingsUpdate
] = None,
global_table_global_secondary_index_settings_update: Optional[
GlobalTableGlobalSecondaryIndexSettingsUpdateList
] = None,
replica_settings_update: Optional[ReplicaSettingsUpdateList] = None,
) -> UpdateGlobalTableSettingsOutput
Updates settings for a global table.
This documentation is for version 2017.11.29 (Legacy) of global tables, which should be avoided for new global tables. Customers should use Global Tables version 2019.11.21 (Current) when possible, because it provides greater flexibility, higher efficiency, and consumes less write capacity than 2017.11.29 (Legacy).
To determine which version you're using, see Determining the global table version you are using. To update existing global tables from version 2017.11.29 (Legacy) to version 2019.11.21 (Current), see Upgrading global tables.
Parameters:
-
global_table_name(TableName) –The name of the global table
-
global_table_billing_mode(Optional[BillingMode], default:None) –The billing mode of the global table. If
GlobalTableBillingModeis not specified, the global table defaults toPROVISIONEDcapacity billing mode.-
PROVISIONED- We recommend usingPROVISIONEDfor predictable workloads.PROVISIONEDsets the billing mode to Provisioned capacity mode. -
PAY_PER_REQUEST- We recommend usingPAY_PER_REQUESTfor unpredictable workloads.PAY_PER_REQUESTsets the billing mode to On-demand capacity mode.
-
-
global_table_provisioned_write_capacity_units(Optional[PositiveLongObject], default:None) –The maximum number of writes consumed per second before DynamoDB returns a
ThrottlingException. -
global_table_provisioned_write_capacity_auto_scaling_settings_update(Optional[AutoScalingSettingsUpdate], default:None) –Auto scaling settings for managing provisioned write capacity for the global table.
-
global_table_global_secondary_index_settings_update(Optional[GlobalTableGlobalSecondaryIndexSettingsUpdateList], default:None) –Represents the settings of a global secondary index for a global table that will be modified.
-
replica_settings_update(Optional[ReplicaSettingsUpdateList], default:None) –Represents the settings for a global table in a Region that will be modified.
Raises:
-
GlobalTableNotFoundException–The specified global table does not exist.
-
IndexNotFoundException–The operation tried to access a nonexistent index.
-
InternalServerError–An error occurred on the server side.
-
LimitExceededException–There is no limit to the number of daily on-demand backups that can be taken.
For most purposes, up to 500 simultaneous table operations are allowed per account. These operations include
CreateTable,UpdateTable,DeleteTable,UpdateTimeToLive,RestoreTableFromBackup, andRestoreTableToPointInTime.When you are creating a table with one or more secondary indexes, you can have up to 250 such requests running at a time. However, if the table or index specifications are complex, then DynamoDB might temporarily reduce the number of concurrent operations.
When importing into DynamoDB, up to 50 simultaneous import table operations are allowed per account.
There is a soft account quota of 2,500 tables.
GetRecords was called with a value of more than 1000 for the limit request parameter.
More than 2 processes are reading from the same streams shard at the same time. Exceeding this limit may result in request throttling.
-
ReplicaNotFoundException–The specified replica is no longer part of the global table.
-
ResourceInUseException–The operation conflicts with the resource's availability. For example:
-
You attempted to recreate an existing table.
-
You tried to delete a table currently in the
CREATINGstate. -
You tried to update a resource that was already being updated.
When appropriate, wait for the ongoing update to complete and attempt the request again.
-
-
UnknownServiceError–The service returned an error code this client does not model.
Source code in docs_src/capo_dynamodb/_services/async_dynamo_db.py
4195 4196 4197 4198 4199 4200 4201 4202 4203 4204 4205 4206 4207 4208 4209 4210 4211 4212 4213 4214 4215 4216 4217 4218 4219 4220 4221 4222 4223 4224 4225 4226 4227 4228 4229 4230 4231 4232 4233 4234 4235 4236 4237 4238 4239 4240 4241 4242 4243 4244 4245 4246 4247 4248 4249 4250 4251 4252 4253 4254 4255 4256 4257 4258 4259 4260 4261 4262 4263 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278 4279 4280 4281 4282 4283 4284 | |