AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
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.
BatchWriteItem cannot update items. To update items, use the
DeleteItem operations specified
BatchWriteItem are atomic; however
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
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
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
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 in the Amazon DynamoDB Developer Guide.
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
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,
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
request. For example, you cannot put and delete the same item in the same
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.
This is an asynchronous operation using the standard naming convention for .NET 4.5 or higher. For .NET 3.5 the operation is implemented as a pair of methods using the standard naming convention of BeginBatchWriteItem and EndBatchWriteItem.
public abstract Task<BatchWriteItemResponse> BatchWriteItemAsync( Dictionary<String, List<WriteRequest>> requestItems, CancellationToken cancellationToken )
A map of one or more table names and, for each table, a list of operations to be performed (DeleteRequest or PutRequest). Each element in the map consists of the following: DeleteRequest - Perform a DeleteItem operation on the specified item. The item to be deleted is identified by a Key subelement: Key - A map of primary key attribute values that uniquely identify the item. Each entry in this map consists of an attribute name and an attribute value. For each primary key, you must provide all of the key attributes. For example, with a simple primary key, you only need to provide a value for the partition key. For a composite primary key, you must provide values for both the partition key and the sort key. PutRequest - Perform a PutItem operation on the specified item. The item to be put is identified by an Item subelement: Item - A map of attributes and their values. Each entry in this map consists of an attribute name and an attribute value. Attribute values must not be null; string and binary type attributes must have lengths greater than zero; and set type attributes must not be empty. Requests that contain empty values will be rejected with a ValidationException exception. If you specify any attributes that are part of an index key, then the data types for those attributes must match those of the schema in the table's attribute definition.
A cancellation token that can be used by other objects or threads to receive notice of cancellation.
|InternalServerErrorException||An error occurred on the server side.|
|ItemCollectionSizeLimitExceededException||An item collection is too large. This exception is only returned for tables that have one or more local secondary indexes.|
|ProvisionedThroughputExceededException||Your request rate is too high. The AWS SDKs for DynamoDB automatically retry requests that receive this exception. Your request is eventually successful, unless your retry queue is too large to finish. Reduce the frequency of requests and use exponential backoff. For more information, go to Error Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.|
|ResourceNotFoundException||The operation tried to access a nonexistent table or index. The resource might not be specified correctly, or its status might not be ACTIVE.|
Supported in: 1.3
Supported in: 4.5
Portable Class Library:
Supported in: Windows Store Apps
Supported in: Windows Phone 8.1
Supported in: Xamarin Android
Supported in: Xamarin iOS (Unified)
Supported in: Xamarin.Forms