Class: Aws::DynamoDB::Client
- Inherits:
-
Seahorse::Client::Base
- Object
- Seahorse::Client::Base
- Aws::DynamoDB::Client
- Includes:
- ClientStubs
- Defined in:
- lib/aws-sdk-dynamodb/customizations/client.rb,
lib/aws-sdk-dynamodb/client.rb
Class Attribute Summary collapse
- .identifier ⇒ Object readonly private
API Operations collapse
-
#batch_get_item(params = {}) ⇒ Types::BatchGetItemOutput
The ‘BatchGetItem` operation returns the attributes of one or more items from one or more tables.
-
#batch_write_item(params = {}) ⇒ Types::BatchWriteItemOutput
The ‘BatchWriteItem` operation puts or deletes multiple items in one or more tables.
-
#create_backup(params = {}) ⇒ Types::CreateBackupOutput
Creates a backup for an existing table.
-
#create_global_table(params = {}) ⇒ Types::CreateGlobalTableOutput
Creates a global table from an existing table.
-
#create_table(params = {}) ⇒ Types::CreateTableOutput
The ‘CreateTable` operation adds a new table to your account.
-
#delete_backup(params = {}) ⇒ Types::DeleteBackupOutput
Deletes an existing backup of a table.
-
#delete_item(params = {}) ⇒ Types::DeleteItemOutput
Deletes a single item in a table by primary key.
-
#delete_table(params = {}) ⇒ Types::DeleteTableOutput
The ‘DeleteTable` operation deletes a table and all of its items.
-
#describe_backup(params = {}) ⇒ Types::DescribeBackupOutput
Describes an existing backup of a table.
-
#describe_continuous_backups(params = {}) ⇒ Types::DescribeContinuousBackupsOutput
Checks the status of continuous backups and point in time recovery on the specified table.
-
#describe_endpoints(params = {}) ⇒ Types::DescribeEndpointsResponse
Returns the regional endpoint information.
-
#describe_global_table(params = {}) ⇒ Types::DescribeGlobalTableOutput
Returns information about the specified global table.
-
#describe_global_table_settings(params = {}) ⇒ Types::DescribeGlobalTableSettingsOutput
Describes region specific settings for a global table.
-
#describe_limits(params = {}) ⇒ Types::DescribeLimitsOutput
Returns the current provisioned-capacity limits for your AWS account in a region, both for the region as a whole and for any one DynamoDB table that you create there.
-
#describe_table(params = {}) ⇒ Types::DescribeTableOutput
Returns information about the table, including the current status of the table, when it was created, the primary key schema, and any indexes on the table.
-
#describe_time_to_live(params = {}) ⇒ Types::DescribeTimeToLiveOutput
Gives a description of the Time to Live (TTL) status on the specified table.
-
#get_item(params = {}) ⇒ Types::GetItemOutput
The ‘GetItem` operation returns a set of attributes for the item with the given primary key.
-
#list_backups(params = {}) ⇒ Types::ListBackupsOutput
List backups associated with an AWS account.
-
#list_global_tables(params = {}) ⇒ Types::ListGlobalTablesOutput
Lists all global tables that have a replica in the specified region.
-
#list_tables(params = {}) ⇒ Types::ListTablesOutput
Returns an array of table names associated with the current account and endpoint.
-
#list_tags_of_resource(params = {}) ⇒ Types::ListTagsOfResourceOutput
List all tags on an Amazon DynamoDB resource.
-
#put_item(params = {}) ⇒ Types::PutItemOutput
Creates a new item, or replaces an old item with a new item.
-
#query(params = {}) ⇒ Types::QueryOutput
The ‘Query` operation finds items based on primary key values.
-
#restore_table_from_backup(params = {}) ⇒ Types::RestoreTableFromBackupOutput
Creates a new table from an existing backup.
-
#restore_table_to_point_in_time(params = {}) ⇒ Types::RestoreTableToPointInTimeOutput
Restores the specified table to the specified point in time within ‘EarliestRestorableDateTime` and `LatestRestorableDateTime`.
-
#scan(params = {}) ⇒ Types::ScanOutput
The ‘Scan` operation returns one or more items and item attributes by accessing every item in a table or a secondary index.
-
#tag_resource(params = {}) ⇒ Struct
Associate a set of tags with an Amazon DynamoDB resource.
-
#transact_get_items(params = {}) ⇒ Types::TransactGetItemsOutput
‘TransactGetItems` is a synchronous operation that atomically retrieves multiple items from one or more tables (but not from indexes) in a single account and region.
-
#transact_write_items(params = {}) ⇒ Types::TransactWriteItemsOutput
‘TransactWriteItems` is a synchronous write operation that groups up to 10 action requests.
-
#untag_resource(params = {}) ⇒ Struct
Removes the association of tags from an Amazon DynamoDB resource.
-
#update_continuous_backups(params = {}) ⇒ Types::UpdateContinuousBackupsOutput
‘UpdateContinuousBackups` enables or disables point in time recovery for the specified table.
-
#update_global_table(params = {}) ⇒ Types::UpdateGlobalTableOutput
Adds or removes replicas in the specified global table.
-
#update_global_table_settings(params = {}) ⇒ Types::UpdateGlobalTableSettingsOutput
Updates settings for a global table.
-
#update_item(params = {}) ⇒ Types::UpdateItemOutput
Edits an existing item’s attributes, or adds a new item to the table if it does not already exist.
-
#update_table(params = {}) ⇒ Types::UpdateTableOutput
Modifies the provisioned throughput settings, global secondary indexes, or DynamoDB Streams settings for a given table.
-
#update_time_to_live(params = {}) ⇒ Types::UpdateTimeToLiveOutput
The UpdateTimeToLive method will enable or disable TTL for the specified table.
Class Method Summary collapse
- .errors_module ⇒ Object private
Instance Method Summary collapse
- #build_request(operation_name, params = {}) ⇒ Object private
-
#initialize(options) ⇒ Client
constructor
A new instance of Client.
- #stub_data(operation_name, data = {}) ⇒ Object
-
#wait_until(waiter_name, params = {}, options = {}) {|w.waiter| ... } ⇒ Boolean
Polls an API operation until a resource enters a desired state.
- #waiter_names ⇒ Object deprecated private Deprecated.
Constructor Details
#initialize(options) ⇒ Client
Returns a new instance of Client.
239 240 241 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 239 def initialize(*args) super end |
Class Attribute Details
.identifier ⇒ Object (readonly)
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
5408 5409 5410 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 5408 def identifier @identifier end |
Class Method Details
.errors_module ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
5411 5412 5413 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 5411 def errors_module Errors end |
Instance Method Details
#batch_get_item(params = {}) ⇒ Types::BatchGetItemOutput
The ‘BatchGetItem` operation returns the attributes of one or more items from one or more tables. You identify requested items by primary key.
A single operation can retrieve up to 16 MB of data, which can contain as many as 100 items. ‘BatchGetItem` will return a partial result if the response size limit is exceeded, the table’s provisioned throughput is exceeded, or an internal processing failure occurs. If a partial result is returned, the operation returns a value for ‘UnprocessedKeys`. You can use this value to retry the operation starting with the next item to get.
If you request more than 100 items ‘BatchGetItem` will return a `ValidationException` with the message “Too many items requested for the BatchGetItem call”.
For example, if you ask to retrieve 100 items, but each individual item is 300 KB in size, the system returns 52 items (so as not to exceed the 16 MB limit). It also returns an appropriate ‘UnprocessedKeys` value so you can get the next page of results. If desired, your application can include its own logic to assemble the pages of results into one data set.
If none of the items can be processed due to insufficient provisioned throughput on all of the tables in the request, then ‘BatchGetItem` will return a `ProvisionedThroughputExceededException`. If *at least one* of the items is successfully processed, then `BatchGetItem` completes successfully, while returning the keys of the unread items in `UnprocessedKeys`.
If DynamoDB returns any unprocessed items, you should retry the batch operation on those items. However, *we strongly recommend that you use an exponential backoff algorithm*. If you retry the batch operation immediately, the underlying read or write requests can still fail due to throttling on the individual tables. If you delay the batch operation using exponential backoff, the individual requests in the batch are much more likely to succeed.
For more information, see [Batch Operations and Error Handling][1] in
the *Amazon DynamoDB Developer Guide*.
By default, ‘BatchGetItem` performs eventually consistent reads on every table in the request. If you want strongly consistent reads instead, you can set `ConsistentRead` to `true` for any or all tables.
In order to minimize response latency, ‘BatchGetItem` retrieves items in parallel.
When designing your application, keep in mind that DynamoDB does not return items in any particular order. To help parse the response by item, include the primary key values for the items in your request in the ‘ProjectionExpression` parameter.
If a requested item does not exist, it is not returned in the result. Requests for nonexistent items consume the minimum read capacity units according to the type of read. For more information, see [Capacity Units Calculations] in the *Amazon DynamoDB Developer Guide*.
[1]: docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#BatchOperations [2]: docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithTables.html#CapacityUnitCalculations
475 476 477 478 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 475 def batch_get_item(params = {}, = {}) req = build_request(:batch_get_item, params) req.send_request() end |
#batch_write_item(params = {}) ⇒ Types::BatchWriteItemOutput
The ‘BatchWriteItem` operation puts or deletes multiple items in one or more tables. A single call to `BatchWriteItem` can write up to 16 MB of data, which can comprise as many as 25 put or delete requests. Individual items to be written can be as large as 400 KB.
<note markdown=“1”> ‘BatchWriteItem` cannot update items. To update items, use the `UpdateItem` action.
</note>
The individual ‘PutItem` and `DeleteItem` operations specified in `BatchWriteItem` are atomic; however `BatchWriteItem` as a whole is not. If any requested operations fail because the table’s provisioned throughput is exceeded or an internal processing failure occurs, the failed operations are returned in the ‘UnprocessedItems` response parameter. You can investigate and optionally resend the requests. Typically, you would call `BatchWriteItem` in a loop. Each iteration would check for unprocessed items and submit a new `BatchWriteItem` request with those unprocessed items until all items have been processed.
Note that if none of the items can be processed due to insufficient provisioned throughput on all of the tables in the request, then ‘BatchWriteItem` will return a `ProvisionedThroughputExceededException`.
If DynamoDB returns any unprocessed items, you should retry the batch operation on those items. However, *we strongly recommend that you use an exponential backoff algorithm*. If you retry the batch operation immediately, the underlying read or write requests can still fail due to throttling on the individual tables. If you delay the batch operation using exponential backoff, the individual requests in the batch are much more likely to succeed.
For more information, see [Batch Operations and Error Handling][1] in
the *Amazon DynamoDB Developer Guide*.
With ‘BatchWriteItem`, you can efficiently write or delete large amounts of data, such as from Amazon Elastic MapReduce (EMR), or copy data from another database into DynamoDB. In order to improve performance with these large-scale operations, `BatchWriteItem` does not behave in the same way as individual `PutItem` and `DeleteItem` calls would. For example, you cannot specify conditions on individual put and delete requests, and `BatchWriteItem` does not return deleted items in the response.
If you use a programming language that supports concurrency, you can use threads to write items in parallel. Your application must include the necessary logic to manage the threads. With languages that don’t support threading, you must update or delete the specified items one at a time. In both situations, ‘BatchWriteItem` performs the specified put and delete operations in parallel, giving you the power of the thread pool approach without having to introduce complexity into your application.
Parallel processing reduces latency, but each specified put and delete request consumes the same number of write capacity units whether it is processed in parallel or not. Delete operations on nonexistent items consume one write capacity unit.
If one or more of the following is true, DynamoDB rejects the entire batch write operation:
-
One or more tables specified in the ‘BatchWriteItem` request does not exist.
-
Primary key attributes specified on an item in the request do not match those in the corresponding table’s primary key schema.
-
You try to perform multiple operations on the same item in the same ‘BatchWriteItem` request. For example, you cannot put and delete the same item in the same `BatchWriteItem` request.
-
Your request contains at least two items with identical hash and range keys (which essentially is two put operations).
-
There are more than 25 requests in the batch.
-
Any individual item in a batch exceeds 400 KB.
-
The total request size exceeds 16 MB.
[1]: docs.aws.amazon.com/amazondynamodb/latest/developerguide/ErrorHandling.html#BatchOperations
685 686 687 688 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 685 def batch_write_item(params = {}, = {}) req = build_request(:batch_write_item, params) req.send_request() end |
#build_request(operation_name, params = {}) ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
5271 5272 5273 5274 5275 5276 5277 5278 5279 5280 5281 5282 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 5271 def build_request(operation_name, params = {}) handlers = @handlers.for(operation_name) context = Seahorse::Client::RequestContext.new( operation_name: operation_name, operation: config.api.operation(operation_name), client: self, params: params, config: config) context[:gem_name] = 'aws-sdk-dynamodb' context[:gem_version] = '1.21.0' Seahorse::Client::Request.new(handlers, context) end |
#create_backup(params = {}) ⇒ Types::CreateBackupOutput
Creates a backup for an existing table.
Each time you create an On-Demand Backup, the entire table data is backed up. There is no limit to the number of on-demand backups that can be taken.
When you create an On-Demand Backup, a time marker of the request is cataloged, and the backup is created asynchronously, by applying all changes until the time of the request to the last full table snapshot. Backup requests are processed instantaneously and become available for restore within minutes.
You can call ‘CreateBackup` at a maximum rate of 50 times per second.
All backups in DynamoDB work without consuming any provisioned throughput on the table.
If you submit a backup request on 2018-12-14 at 14:25:00, the backup is guaranteed to contain all data committed to the table up to 14:24:00, and data committed after 14:26:00 will not be. The backup may or may not contain data modifications made between 14:24:00 and 14:26:00. On-Demand Backup does not support causal consistency.
Along with data, the following are also included on the backups:
-
Global secondary indexes (GSIs)
-
Local secondary indexes (LSIs)
-
Streams
-
Provisioned read and write capacity
754 755 756 757 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 754 def create_backup(params = {}, = {}) req = build_request(:create_backup, params) req.send_request() end |
#create_global_table(params = {}) ⇒ Types::CreateGlobalTableOutput
Creates a global table from an existing table. A global table creates a replication relationship between two or more DynamoDB tables with the same table name in the provided regions.
If you want to add a new replica table to a global table, each of the following conditions must be true:
-
The table must have the same primary key as all of the other replicas.
-
The table must have the same name as all of the other replicas.
-
The table must have DynamoDB Streams enabled, with the stream containing both the new and the old images of the item.
-
None of the replica tables in the global table can contain any data.
If global secondary indexes are specified, then the following conditions must also be met:
-
The global secondary indexes must have the same name.
-
The global secondary indexes must have the same hash key and sort key (if present).
Write capacity settings should be set consistently across your replica tables and secondary indexes. DynamoDB strongly recommends enabling auto scaling to manage the write capacity settings for all of your global tables replicas and indexes.
If you prefer to manage write capacity settings manually, you should
provision equal replicated write capacity units to your replica tables. You should also provision equal replicated write capacity units to matching secondary indexes across your global table.
828 829 830 831 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 828 def create_global_table(params = {}, = {}) req = build_request(:create_global_table, params) req.send_request() end |
#create_table(params = {}) ⇒ Types::CreateTableOutput
The ‘CreateTable` operation adds a new table to your account. In an AWS account, table names must be unique within each region. That is, you can have two tables with same name if you create the tables in different regions.
‘CreateTable` is an asynchronous operation. Upon receiving a `CreateTable` request, DynamoDB immediately returns a response with a `TableStatus` of `CREATING`. After the table is created, DynamoDB sets the `TableStatus` to `ACTIVE`. You can perform read and write operations only on an `ACTIVE` table.
You can optionally define secondary indexes on the new table, as part of the ‘CreateTable` operation. If you want to create multiple tables with secondary indexes on them, you must create the tables sequentially. Only one table with secondary indexes can be in the `CREATING` state at any given time.
You can use the ‘DescribeTable` action to check the table status.
1174 1175 1176 1177 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 1174 def create_table(params = {}, = {}) req = build_request(:create_table, params) req.send_request() end |
#delete_backup(params = {}) ⇒ Types::DeleteBackupOutput
Deletes an existing backup of a table.
You can call ‘DeleteBackup` at a maximum rate of 10 times per second.
1247 1248 1249 1250 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 1247 def delete_backup(params = {}, = {}) req = build_request(:delete_backup, params) req.send_request() end |
#delete_item(params = {}) ⇒ Types::DeleteItemOutput
Deletes a single item in a table by primary key. You can perform a conditional delete operation that deletes the item if it exists, or if it has an expected attribute value.
In addition to deleting an item, you can also return the item’s attribute values in the same operation, using the ‘ReturnValues` parameter.
Unless you specify conditions, the ‘DeleteItem` is an idempotent operation; running it multiple times on the same item or attribute does not result in an error response.
Conditional deletes are useful for deleting items only if specific conditions are met. If those conditions are met, DynamoDB performs the delete. Otherwise, the item is not deleted.
1499 1500 1501 1502 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 1499 def delete_item(params = {}, = {}) req = build_request(:delete_item, params) req.send_request() end |
#delete_table(params = {}) ⇒ Types::DeleteTableOutput
The ‘DeleteTable` operation deletes a table and all of its items. After a `DeleteTable` request, the specified table is in the `DELETING` state until DynamoDB completes the deletion. If the table is in the `ACTIVE` state, you can delete it. If a table is in `CREATING` or `UPDATING` states, then DynamoDB returns a `ResourceInUseException`. If the specified table does not exist, DynamoDB returns a `ResourceNotFoundException`. If table is already in the `DELETING` state, no error is returned.
<note markdown=“1”> DynamoDB might continue to accept data read and write operations, such as ‘GetItem` and `PutItem`, on a table in the `DELETING` state until the table deletion is complete.
</note>
When you delete a table, any indexes on that table are also deleted.
If you have DynamoDB Streams enabled on the table, then the corresponding stream on that table goes into the ‘DISABLED` state, and the stream is automatically deleted after 24 hours.
Use the ‘DescribeTable` action to check the status of the table.
1607 1608 1609 1610 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 1607 def delete_table(params = {}, = {}) req = build_request(:delete_table, params) req.send_request() end |
#describe_backup(params = {}) ⇒ Types::DescribeBackupOutput
Describes an existing backup of a table.
You can call ‘DescribeBackup` at a maximum rate of 10 times per second.
1681 1682 1683 1684 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 1681 def describe_backup(params = {}, = {}) req = build_request(:describe_backup, params) req.send_request() end |
#describe_continuous_backups(params = {}) ⇒ Types::DescribeContinuousBackupsOutput
Checks the status of continuous backups and point in time recovery on the specified table. Continuous backups are ‘ENABLED` on all tables at table creation. If point in time recovery is enabled, `PointInTimeRecoveryStatus` will be set to ENABLED.
Once continuous backups and point in time recovery are enabled, you can restore to any point in time within ‘EarliestRestorableDateTime` and `LatestRestorableDateTime`.
‘LatestRestorableDateTime` is typically 5 minutes before the current time. You can restore your table to any point in time during the last 35 days.
You can call ‘DescribeContinuousBackups` at a maximum rate of 10 times per second.
1727 1728 1729 1730 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 1727 def describe_continuous_backups(params = {}, = {}) req = build_request(:describe_continuous_backups, params) req.send_request() end |
#describe_endpoints(params = {}) ⇒ Types::DescribeEndpointsResponse
Returns the regional endpoint information.
1748 1749 1750 1751 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 1748 def describe_endpoints(params = {}, = {}) req = build_request(:describe_endpoints, params) req.send_request() end |
#describe_global_table(params = {}) ⇒ Types::DescribeGlobalTableOutput
Returns information about the specified global table.
1781 1782 1783 1784 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 1781 def describe_global_table(params = {}, = {}) req = build_request(:describe_global_table, params) req.send_request() end |
#describe_global_table_settings(params = {}) ⇒ Types::DescribeGlobalTableSettingsOutput
Describes region specific settings for a global table.
1862 1863 1864 1865 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 1862 def describe_global_table_settings(params = {}, = {}) req = build_request(:describe_global_table_settings, params) req.send_request() end |
#describe_limits(params = {}) ⇒ Types::DescribeLimitsOutput
Returns the current provisioned-capacity limits for your AWS account in a region, both for the region as a whole and for any one DynamoDB table that you create there.
When you establish an AWS account, the account has initial limits on the maximum read capacity units and write capacity units that you can provision across all of your DynamoDB tables in a given region. Also, there are per-table limits that apply when you create a table there. For more information, see [Limits] page in the *Amazon DynamoDB Developer Guide*.
Although you can increase these limits by filing a case at [AWS Support Center], obtaining the increase is not instantaneous. The ‘DescribeLimits` action lets you write code to compare the capacity you are currently using to those limits imposed by your account so that you have enough time to apply for an increase before you hit a limit.
For example, you could use one of the AWS SDKs to do the following:
-
Call ‘DescribeLimits` for a particular region to obtain your current account limits on provisioned capacity there.
-
Create a variable to hold the aggregate read capacity units provisioned for all your tables in that region, and one to hold the aggregate write capacity units. Zero them both.
-
Call ‘ListTables` to obtain a list of all your DynamoDB tables.
-
For each table name listed by ‘ListTables`, do the following:
-
Call ‘DescribeTable` with the table name.
-
Use the data returned by ‘DescribeTable` to add the read capacity units and write capacity units provisioned for the table itself to your variables.
-
If the table has one or more global secondary indexes (GSIs), loop over these GSIs and add their provisioned capacity values to your variables as well.
-
-
Report the account limits for that region returned by ‘DescribeLimits`, along with the total current provisioned capacity levels you have calculated.
This will let you see whether you are getting close to your account-level limits.
The per-table limits apply only when you are creating a new table. They restrict the sum of the provisioned capacity of the new table itself and all its global secondary indexes.
For existing tables and their GSIs, DynamoDB will not let you increase provisioned capacity extremely rapidly, but the only upper limit that applies is that the aggregate provisioned capacity over all your tables and GSIs cannot exceed either of the per-account limits.
<note markdown=“1”> ‘DescribeLimits` should only be called periodically. You can expect throttling errors if you call it more than once in a minute.
</note>
The ‘DescribeLimits` Request element has no content.
[1]: docs.aws.amazon.com/amazondynamodb/latest/developerguide/Limits.html [2]: console.aws.amazon.com/support/home#/
1954 1955 1956 1957 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 1954 def describe_limits(params = {}, = {}) req = build_request(:describe_limits, params) req.send_request() end |
#describe_table(params = {}) ⇒ Types::DescribeTableOutput
Returns information about the table, including the current status of the table, when it was created, the primary key schema, and any indexes on the table.
<note markdown=“1”> If you issue a ‘DescribeTable` request immediately after a `CreateTable` request, DynamoDB might return a `ResourceNotFoundException`. This is because `DescribeTable` uses an eventually consistent query, and the metadata for your table might not be available at that moment. Wait for a few seconds, and then try the `DescribeTable` request again.
</note>
2052 2053 2054 2055 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 2052 def describe_table(params = {}, = {}) req = build_request(:describe_table, params) req.send_request() end |
#describe_time_to_live(params = {}) ⇒ Types::DescribeTimeToLiveOutput
Gives a description of the Time to Live (TTL) status on the specified table.
2082 2083 2084 2085 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 2082 def describe_time_to_live(params = {}, = {}) req = build_request(:describe_time_to_live, params) req.send_request() end |
#get_item(params = {}) ⇒ Types::GetItemOutput
The ‘GetItem` operation returns a set of attributes for the item with the given primary key. If there is no matching item, `GetItem` does not return any data and there will be no `Item` element in the response.
‘GetItem` provides an eventually consistent read by default. If your application requires a strongly consistent read, set `ConsistentRead` to `true`. Although a strongly consistent read might take more time than an eventually consistent read, it always returns the last updated value.
2254 2255 2256 2257 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 2254 def get_item(params = {}, = {}) req = build_request(:get_item, params) req.send_request() end |
#list_backups(params = {}) ⇒ Types::ListBackupsOutput
List backups associated with an AWS account. To list backups for a given table, specify ‘TableName`. `ListBackups` returns a paginated list of results with at most 1MB worth of items in a page. You can also specify a limit for the maximum number of entries to be returned in a page.
In the request, start time is inclusive but end time is exclusive. Note that these limits are for the time at which the original backup was requested.
You can call ‘ListBackups` a maximum of 5 times per second.
2338 2339 2340 2341 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 2338 def list_backups(params = {}, = {}) req = build_request(:list_backups, params) req.send_request() end |
#list_global_tables(params = {}) ⇒ Types::ListGlobalTablesOutput
Lists all global tables that have a replica in the specified region.
2379 2380 2381 2382 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 2379 def list_global_tables(params = {}, = {}) req = build_request(:list_global_tables, params) req.send_request() end |
#list_tables(params = {}) ⇒ Types::ListTablesOutput
Returns an array of table names associated with the current account and endpoint. The output from ‘ListTables` is paginated, with each page returning a maximum of 100 table names.
2419 2420 2421 2422 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 2419 def list_tables(params = {}, = {}) req = build_request(:list_tables, params) req.send_request() end |
#list_tags_of_resource(params = {}) ⇒ Types::ListTagsOfResourceOutput
List all tags on an Amazon DynamoDB resource. You can call ListTagsOfResource up to 10 times per second, per account.
For an overview on tagging DynamoDB resources, see [Tagging for DynamoDB] in the *Amazon DynamoDB Developer Guide*.
[1]: docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html
2466 2467 2468 2469 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 2466 def (params = {}, = {}) req = build_request(:list_tags_of_resource, params) req.send_request() end |
#put_item(params = {}) ⇒ Types::PutItemOutput
Creates a new item, or replaces an old item with a new item. If an item that has the same primary key as the new item already exists in the specified table, the new item completely replaces the existing item. You can perform a conditional put operation (add a new item if one with the specified primary key doesn’t exist), or replace an existing item if it has certain attribute values. You can return the item’s attribute values in the same operation, using the ‘ReturnValues` parameter.
This topic provides general information about the ‘PutItem` API.
For information on how to call the `PutItem` API using the AWS SDK in
specific languages, see the following:
* [ PutItem in the AWS Command Line Interface ][1]
- PutItem in the AWS SDK for .NET ][2
- PutItem in the AWS SDK for C++ ][3
- PutItem in the AWS SDK for Go ][4
- PutItem in the AWS SDK for Java ][5
- PutItem in the AWS SDK for JavaScript ][6
- PutItem in the AWS SDK for PHP V3 ][7
- PutItem in the AWS SDK for Python ][8
- PutItem in the AWS SDK for Ruby V2 ][9
When you add an item, the primary key attribute(s) are the only required attributes. Attribute values cannot be null. String and Binary type attributes must have lengths greater than zero. Set type attributes cannot be empty. Requests with empty values will be rejected with a ‘ValidationException` exception.
<note markdown=“1”> To prevent a new item from replacing an existing item, use a conditional expression that contains the ‘attribute_not_exists` function with the name of the attribute being used as the partition key for the table. Since every record must contain that attribute, the `attribute_not_exists` function will only succeed if no matching item exists.
</note>
For more information about ‘PutItem`, see [Working with Items] in the *Amazon DynamoDB Developer Guide*.
[1]: docs.aws.amazon.com/goto/aws-cli/dynamodb-2012-08-10/PutItem [2]: docs.aws.amazon.com/goto/DotNetSDKV3/dynamodb-2012-08-10/PutItem [3]: docs.aws.amazon.com/goto/SdkForCpp/dynamodb-2012-08-10/PutItem [4]: docs.aws.amazon.com/goto/SdkForGoV1/dynamodb-2012-08-10/PutItem [5]: docs.aws.amazon.com/goto/SdkForJava/dynamodb-2012-08-10/PutItem [6]: docs.aws.amazon.com/goto/AWSJavaScriptSDK/dynamodb-2012-08-10/PutItem [7]: docs.aws.amazon.com/goto/SdkForPHPV3/dynamodb-2012-08-10/PutItem [8]: docs.aws.amazon.com/goto/boto3/dynamodb-2012-08-10/PutItem [9]: docs.aws.amazon.com/goto/SdkForRubyV2/dynamodb-2012-08-10/PutItem [10]: docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithItems.html
2780 2781 2782 2783 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 2780 def put_item(params = {}, = {}) req = build_request(:put_item, params) req.send_request() end |
#query(params = {}) ⇒ Types::QueryOutput
The ‘Query` operation finds items based on primary key values. You can query any table or secondary index that has a composite primary key (a partition key and a sort key).
Use the ‘KeyConditionExpression` parameter to provide a specific value for the partition key. The `Query` operation will return all of the items from the table or index with that partition key value. You can optionally narrow the scope of the `Query` operation by specifying a sort key value and a comparison operator in `KeyConditionExpression`. To further refine the `Query` results, you can optionally provide a `FilterExpression`. A `FilterExpression` determines which items within the results should be returned to you. All of the other results are discarded.
A ‘Query` operation always returns a result set. If no matching items are found, the result set will be empty. Queries that do not return results consume the minimum number of read capacity units for that type of read operation.
<note markdown=“1”> DynamoDB calculates the number of read capacity units consumed based on item size, not on the amount of data that is returned to an application. The number of capacity units consumed will be the same whether you request all of the attributes (the default behavior) or just some of them (using a projection expression). The number will also be the same whether or not you use a ‘FilterExpression`.
</note>
‘Query` results are always sorted by the sort key value. If the data type of the sort key is Number, the results are returned in numeric order; otherwise, the results are returned in order of UTF-8 bytes. By default, the sort order is ascending. To reverse the order, set the `ScanIndexForward` parameter to false.
A single ‘Query` operation will read up to the maximum number of items set (if using the `Limit` parameter) or a maximum of 1 MB of data and then apply any filtering to the results using `FilterExpression`. If `LastEvaluatedKey` is present in the response, you will need to paginate the result set. For more information, see [Paginating the Results] in the *Amazon DynamoDB Developer Guide*.
‘FilterExpression` is applied after a `Query` finishes, but before the results are returned. A `FilterExpression` cannot contain partition key or sort key attributes. You need to specify those attributes in the `KeyConditionExpression`.
<note markdown=“1”> A ‘Query` operation can return an empty result set and a `LastEvaluatedKey` if all the items read for the page of results are filtered out.
</note>
You can query a table, a local secondary index, or a global secondary index. For a query on a table or on a local secondary index, you can set the ‘ConsistentRead` parameter to `true` and obtain a strongly consistent result. Global secondary indexes support eventually consistent reads only, so do not specify `ConsistentRead` when querying a global secondary index.
[1]: docs.aws.amazon.com/amazondynamodb/latest/developerguide/Query.html#Query.Pagination
3284 3285 3286 3287 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 3284 def query(params = {}, = {}) req = build_request(:query, params) req.send_request() end |
#restore_table_from_backup(params = {}) ⇒ Types::RestoreTableFromBackupOutput
Creates a new table from an existing backup. Any number of users can execute up to 4 concurrent restores (any type of restore) in a given account.
You can call ‘RestoreTableFromBackup` at a maximum rate of 10 times per second.
You must manually set up the following on the restored table:
-
Auto scaling policies
-
IAM policies
-
Cloudwatch metrics and alarms
-
Tags
-
Stream settings
-
Time to Live (TTL) settings
3394 3395 3396 3397 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 3394 def restore_table_from_backup(params = {}, = {}) req = build_request(:restore_table_from_backup, params) req.send_request() end |
#restore_table_to_point_in_time(params = {}) ⇒ Types::RestoreTableToPointInTimeOutput
Restores the specified table to the specified point in time within ‘EarliestRestorableDateTime` and `LatestRestorableDateTime`. You can restore your table to any point in time during the last 35 days. Any number of users can execute up to 4 concurrent restores (any type of restore) in a given account.
When you restore using point in time recovery, DynamoDB restores your table data to the state based on the selected date and time (day:hour:minute:second) to a new table.
Along with data, the following are also included on the new restored table using point in time recovery:
-
Global secondary indexes (GSIs)
-
Local secondary indexes (LSIs)
-
Provisioned read and write capacity
-
Encryption settings
All these settings come from the current settings of the source table at the time of restore.
You must manually set up the following on the restored table:
-
Auto scaling policies
-
IAM policies
-
Cloudwatch metrics and alarms
-
Tags
-
Stream settings
-
Time to Live (TTL) settings
-
Point in time recovery settings
3533 3534 3535 3536 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 3533 def restore_table_to_point_in_time(params = {}, = {}) req = build_request(:restore_table_to_point_in_time, params) req.send_request() end |
#scan(params = {}) ⇒ Types::ScanOutput
The ‘Scan` operation returns one or more items and item attributes by accessing every item in a table or a secondary index. To have DynamoDB return fewer items, you can provide a `FilterExpression` operation.
If the total number of scanned items exceeds the maximum data set size limit of 1 MB, the scan stops and results are returned to the user as a ‘LastEvaluatedKey` value to continue the scan in a subsequent operation. The results also include the number of items exceeding the limit. A scan can result in no table data meeting the filter criteria.
A single ‘Scan` operation will read up to the maximum number of items set (if using the `Limit` parameter) or a maximum of 1 MB of data and then apply any filtering to the results using `FilterExpression`. If `LastEvaluatedKey` is present in the response, you will need to paginate the result set. For more information, see [Paginating the Results] in the *Amazon DynamoDB Developer Guide*.
‘Scan` operations proceed sequentially; however, for faster performance on a large table or secondary index, applications can request a parallel `Scan` operation by providing the `Segment` and `TotalSegments` parameters. For more information, see [Parallel Scan] in the *Amazon DynamoDB Developer Guide*.
‘Scan` uses eventually consistent reads when accessing the data in a table; therefore, the result set might not include the changes to data in the table immediately before the operation began. If you need a consistent copy of the data, as of the time that the `Scan` begins, you can set the `ConsistentRead` parameter to `true`.
[1]: docs.aws.amazon.com/amazondynamodb/latest/developerguide/Scan.html#Scan.Pagination [2]: docs.aws.amazon.com/amazondynamodb/latest/developerguide/Scan.html#Scan.ParallelScan
3936 3937 3938 3939 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 3936 def scan(params = {}, = {}) req = build_request(:scan, params) req.send_request() end |
#stub_data(operation_name, data = {}) ⇒ Object
5 6 7 8 9 10 11 12 13 14 15 |
# File 'lib/aws-sdk-dynamodb/customizations/client.rb', line 5 def stub_data(operation_name, data = {}) if config.simple_attributes rules = config.api.operation(operation_name).output translator = Plugins::SimpleAttributes::ValueTranslator data = translator.apply(rules, :marshal, data) data = super(operation_name, data) translator.apply(rules, :unmarshal, data) else super end end |
#tag_resource(params = {}) ⇒ Struct
Associate a set of tags with an Amazon DynamoDB resource. You can then activate these user-defined tags so that they appear on the Billing and Cost Management console for cost allocation tracking. You can call TagResource up to 5 times per second, per account.
For an overview on tagging DynamoDB resources, see [Tagging for DynamoDB] in the *Amazon DynamoDB Developer Guide*.
[1]: docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html
3978 3979 3980 3981 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 3978 def tag_resource(params = {}, = {}) req = build_request(:tag_resource, params) req.send_request() end |
#transact_get_items(params = {}) ⇒ Types::TransactGetItemsOutput
‘TransactGetItems` is a synchronous operation that atomically retrieves multiple items from one or more tables (but not from indexes) in a single account and region. A `TransactGetItems` call can contain up to 10 `TransactGetItem` objects, each of which contains a `Get` structure that specifies an item to retrieve from a table in the account and region. A call to `TransactGetItems` cannot retrieve items from tables in more than one AWS account or region.
DynamoDB rejects the entire ‘TransactGetItems` request if any of the following is true:
-
A conflicting operation is in the process of updating an item to be read.
-
There is insufficient provisioned capacity for the transaction to be completed.
-
There is a user error, such as an invalid data format.
4062 4063 4064 4065 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 4062 def transact_get_items(params = {}, = {}) req = build_request(:transact_get_items, params) req.send_request() end |
#transact_write_items(params = {}) ⇒ Types::TransactWriteItemsOutput
‘TransactWriteItems` is a synchronous write operation that groups up to 10 action requests. These actions can target items in different tables, but not in different AWS accounts or regions, and no two actions can target the same item. For example, you cannot both `ConditionCheck` and `Update` the same item.
The actions are completed atomically so that either all of them succeed, or all of them fail. They are defined by the following objects:
-
‘Put` — Initiates a `PutItem` operation to write a new item. This structure specifies the primary key of the item to be written, the name of the table to write it in, an optional condition expression that must be satisfied for the write to succeed, a list of the item’s attributes, and a field indicating whether or not to retrieve the item’s attributes if the condition is not met.
-
‘Update` — Initiates an `UpdateItem` operation to update an existing item. This structure specifies the primary key of the item to be updated, the name of the table where it resides, an optional condition expression that must be satisfied for the update to succeed, an expression that defines one or more attributes to be updated, and a field indicating whether or not to retrieve the item’s attributes if the condition is not met.
-
‘Delete` — Initiates a `DeleteItem` operation to delete an existing item. This structure specifies the primary key of the item to be deleted, the name of the table where it resides, an optional condition expression that must be satisfied for the deletion to succeed, and a field indicating whether or not to retrieve the item’s attributes if the condition is not met.
-
‘ConditionCheck` — Applies a condition to an item that is not being modified by the transaction. This structure specifies the primary key of the item to be checked, the name of the table where it resides, a condition expression that must be satisfied for the transaction to succeed, and a field indicating whether or not to retrieve the item’s attributes if the condition is not met.
DynamoDB rejects the entire ‘TransactWriteItems` request if any of the following is true:
-
A condition in one of the condition expressions is not met.
-
A conflicting operation is in the process of updating the same item.
-
There is insufficient provisioned capacity for the transaction to be completed.
-
An item size becomes too large (bigger than 400 KB), a Local Secondary Index (LSI) becomes too large, or a similar validation error occurs because of changes made by the transaction.
-
There is a user error, such as an invalid data format.
4281 4282 4283 4284 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 4281 def transact_write_items(params = {}, = {}) req = build_request(:transact_write_items, params) req.send_request() end |
#untag_resource(params = {}) ⇒ Struct
Removes the association of tags from an Amazon DynamoDB resource. You can call UntagResource up to 5 times per second, per account.
For an overview on tagging DynamoDB resources, see [Tagging for DynamoDB] in the *Amazon DynamoDB Developer Guide*.
[1]: docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tagging.html
4318 4319 4320 4321 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 4318 def untag_resource(params = {}, = {}) req = build_request(:untag_resource, params) req.send_request() end |
#update_continuous_backups(params = {}) ⇒ Types::UpdateContinuousBackupsOutput
‘UpdateContinuousBackups` enables or disables point in time recovery for the specified table. A successful `UpdateContinuousBackups` call returns the current `ContinuousBackupsDescription`. Continuous backups are `ENABLED` on all tables at table creation. If point in time recovery is enabled, `PointInTimeRecoveryStatus` will be set to ENABLED.
Once continuous backups and point in time recovery are enabled, you can restore to any point in time within ‘EarliestRestorableDateTime` and `LatestRestorableDateTime`.
‘LatestRestorableDateTime` is typically 5 minutes before the current time. You can restore your table to any point in time during the last 35 days..
4368 4369 4370 4371 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 4368 def update_continuous_backups(params = {}, = {}) req = build_request(:update_continuous_backups, params) req.send_request() end |
#update_global_table(params = {}) ⇒ Types::UpdateGlobalTableOutput
Adds or removes replicas in the specified global table. The global table must already exist to be able to use this operation. Any replica to be added must be empty, must have the same name as the global table, must have the same key schema, and must have DynamoDB Streams enabled and must have same provisioned and maximum write capacity units.
<note markdown=“1”> Although you can use ‘UpdateGlobalTable` to add replicas and remove replicas in a single request, for simplicity we recommend that you issue separate requests for adding or removing replicas.
</note>
If global secondary indexes are specified, then the following conditions must also be met:
-
The global secondary indexes must have the same name.
-
The global secondary indexes must have the same hash key and sort key (if present).
-
The global secondary indexes must have the same provisioned and maximum write capacity units.
4437 4438 4439 4440 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 4437 def update_global_table(params = {}, = {}) req = build_request(:update_global_table, params) req.send_request() end |
#update_global_table_settings(params = {}) ⇒ Types::UpdateGlobalTableSettingsOutput
Updates settings for a global table.
4619 4620 4621 4622 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 4619 def update_global_table_settings(params = {}, = {}) req = build_request(:update_global_table_settings, params) req.send_request() end |
#update_item(params = {}) ⇒ Types::UpdateItemOutput
Edits an existing item’s attributes, or adds a new item to the table if it does not already exist. You can put, delete, or add attribute values. You can also perform a conditional update on an existing item (insert a new attribute name-value pair if it doesn’t exist, or replace an existing name-value pair if it has certain expected attribute values).
You can also return the item’s attribute values in the same ‘UpdateItem` operation using the `ReturnValues` parameter.
4979 4980 4981 4982 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 4979 def update_item(params = {}, = {}) req = build_request(:update_item, params) req.send_request() end |
#update_table(params = {}) ⇒ Types::UpdateTableOutput
Modifies the provisioned throughput settings, global secondary indexes, or DynamoDB Streams settings for a given table.
You can only perform one of the following operations at once:
-
Modify the provisioned throughput settings of the table.
-
Enable or disable Streams on the table.
-
Remove a global secondary index from the table.
-
Create a new global secondary index on the table. Once the index begins backfilling, you can use ‘UpdateTable` to perform other operations.
‘UpdateTable` is an asynchronous operation; while it is executing, the table status changes from `ACTIVE` to `UPDATING`. While it is `UPDATING`, you cannot issue another `UpdateTable` request. When the table returns to the `ACTIVE` state, the `UpdateTable` operation is complete.
5190 5191 5192 5193 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 5190 def update_table(params = {}, = {}) req = build_request(:update_table, params) req.send_request() end |
#update_time_to_live(params = {}) ⇒ Types::UpdateTimeToLiveOutput
The UpdateTimeToLive method will enable or disable TTL for the specified table. A successful ‘UpdateTimeToLive` call returns the current `TimeToLiveSpecification`; it may take up to one hour for the change to fully process. Any additional `UpdateTimeToLive` calls for the same table during this one hour duration result in a `ValidationException`.
TTL compares the current time in epoch time format to the time stored in the TTL attribute of an item. If the epoch time value stored in the attribute is less than the current time, the item is marked as expired and subsequently deleted.
<note markdown=“1”> The epoch time format is the number of seconds elapsed since 12:00:00 AM January 1st, 1970 UTC.
</note>
DynamoDB deletes expired items on a best-effort basis to ensure availability of throughput for other data operations.
DynamoDB typically deletes expired items within two days of expiration. The exact duration within which an item gets deleted after expiration is specific to the nature of the workload. Items that have expired and not been deleted will still show up in reads, queries, and scans.
As items are deleted, they are removed from any Local Secondary Index and Global Secondary Index immediately in the same eventually consistent way as a standard delete operation.
For more information, see [Time To Live] in the Amazon DynamoDB Developer Guide.
[1]: docs.aws.amazon.com/amazondynamodb/latest/developerguide/TTL.html
5262 5263 5264 5265 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 5262 def update_time_to_live(params = {}, = {}) req = build_request(:update_time_to_live, params) req.send_request() end |
#wait_until(waiter_name, params = {}, options = {}) {|w.waiter| ... } ⇒ Boolean
Polls an API operation until a resource enters a desired state.
## Basic Usage
A waiter will call an API operation until:
-
It is successful
-
It enters a terminal state
-
It makes the maximum number of attempts
In between attempts, the waiter will sleep.
# polls in a loop, sleeping between attempts
client.waiter_until(waiter_name, params)
## Configuration
You can configure the maximum number of polling attempts, and the delay (in seconds) between each polling attempt. You can pass configuration as the final arguments hash.
# poll for ~25 seconds
client.wait_until(waiter_name, params, {
max_attempts: 5,
delay: 5,
})
## Callbacks
You can be notified before each polling attempt and before each delay. If you throw ‘:success` or `:failure` from these callbacks, it will terminate the waiter.
started_at = Time.now
client.wait_until(waiter_name, params, {
# disable max attempts
max_attempts: nil,
# poll for 1 hour, instead of a number of attempts
before_wait: -> (attempts, response) do
throw :failure if Time.now - started_at > 3600
end
})
## Handling Errors
When a waiter is unsuccessful, it will raise an error. All of the failure errors extend from Waiters::Errors::WaiterFailed.
begin
client.wait_until(...)
rescue Aws::Waiters::Errors::WaiterFailed
# resource did not enter the desired state in time
end
## Valid Waiters
The following table lists the valid waiter names, the operations they call, and the default ‘:delay` and `:max_attempts` values.
| waiter_name | params | :delay | :max_attempts | | —————- | —————– | ——– | ————- | | table_exists | #describe_table | 20 | 25 | | table_not_exists | #describe_table | 20 | 25 |
5373 5374 5375 5376 5377 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 5373 def wait_until(waiter_name, params = {}, = {}) w = waiter(waiter_name, ) yield(w.waiter) if block_given? # deprecated w.wait(params) end |
#waiter_names ⇒ Object
This method is part of a private API. You should avoid using this method if possible, as it may be removed or be changed in the future.
5381 5382 5383 |
# File 'lib/aws-sdk-dynamodb/client.rb', line 5381 def waiter_names waiters.keys end |