Skip to content

Commit 08916a1

Browse files
Update generated code (#1739)
update generated code
1 parent f6174e9 commit 08916a1

File tree

3 files changed

+13
-4
lines changed

3 files changed

+13
-4
lines changed

CHANGELOG.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,10 @@
22

33
## NOT RELEASED
44

5+
### Changed
6+
7+
- AWS enhancement: Documentation updates.
8+
59
## 3.2.1
610

711
### Changed

src/DynamoDbClient.php

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -176,8 +176,11 @@ public function batchGetItem($input): BatchGetItemOutput
176176
* `BatchWriteItem` in a loop. Each iteration would check for unprocessed items and submit a new `BatchWriteItem`
177177
* request with those unprocessed items until all items have been processed.
178178
*
179-
* If *none* of the items can be processed due to insufficient provisioned throughput on all of the tables in the
180-
* request, then `BatchWriteItem` returns a `ProvisionedThroughputExceededException`.
179+
* For tables and indexes with provisioned capacity, if none of the items can be processed due to insufficient
180+
* provisioned throughput on all of the tables in the request, then `BatchWriteItem` returns a
181+
* `ProvisionedThroughputExceededException`. For all tables and indexes, if none of the items can be processed due to
182+
* other throttling scenarios (such as exceeding partition level limits), then `BatchWriteItem` returns a
183+
* `ThrottlingException`.
181184
*
182185
* ! If DynamoDB returns any unprocessed items, you should retry the batch operation on those items. However, *we
183186
* ! strongly recommend that you use an exponential backoff algorithm*. If you retry the batch operation immediately,
@@ -367,7 +370,7 @@ public function deleteItem($input): DeleteItemOutput
367370
* ! For global tables, this operation only applies to global tables using Version 2019.11.21 (Current version).
368371
*
369372
* > DynamoDB might continue to accept data read and write operations, such as `GetItem` and `PutItem`, on a table in
370-
* > the `DELETING` state until the table deletion is complete.
373+
* > the `DELETING` state until the table deletion is complete. For the full list of table states, see TableStatus [^1].
371374
*
372375
* When you delete a table, any indexes on that table are also deleted.
373376
*
@@ -376,6 +379,8 @@ public function deleteItem($input): DeleteItemOutput
376379
*
377380
* Use the `DescribeTable` action to check the status of the table.
378381
*
382+
* [^1]: https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_TableDescription.html#DDB-Type-TableDescription-TableStatus
383+
*
379384
* @see https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_DeleteTable.html
380385
* @see https://docs.aws.amazon.com/aws-sdk-php/v3/api/api-dynamodb-2012-08-10.html#deletetable
381386
*

src/Result/QueryOutput.php

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ class QueryOutput extends Result implements \IteratorAggregate
4545
*
4646
* If you did not use a filter in the request, then `ScannedCount` is the same as `Count`.
4747
*
48-
* [^1]: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/QueryAndScan.html#Count
48+
* [^1]: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Scan.html#Scan.Count
4949
*
5050
* @var int|null
5151
*/

0 commit comments

Comments
 (0)