The AWS SDK client with which to communicate with DynamoDB.
A synchronous or asynchronous iterable of tuples describing the operations to execute. The first member of the tuple should be the name of the table targeted by the operation.
The AWS SDK client with which to communicate with DynamoDB.
Items that have been retrieved and are ready to be returned.
A mapping of table names to table-specific operation state (e.g., the number of throttling events experienced, etc.)
Input elements that are prepared for immediate dispatch
Create and return the initial state object for a given DynamoDB table.
The name of the table whose initial state should be returned.
Accept an array of unprocessed items belonging to a single table and re-enqueue it for submission, making sure the appropriate level of backoff is applied to future operations on the same table.
The table to which the unprocessed elements belong.
Elements returned by DynamoDB as not yet processed. The elements should not be unmarshalled, but they should be reverted to the form used for elements that have not yet been sent.
Iterate over all pending writes and move those targeting throttled tables into the throttled queue.
A set of tables for which some items were returned without being processed.
Puts or deletes items from DynamoDB in batches of 25 or fewer via one or more BatchWriteItem operations. The items may belong to any number of tables.
The iterable of writes to perform may be synchronous or asynchronous and is expected to yield tuples describing the writes to be performed. The first member should be the table name, and the second should be {WriteRequest} object that defines either a put request or a delete request.
This method will automatically retry any write requests returned by DynamoDB as unprocessed. Exponential backoff on unprocessed items is employed on a per-table basis.