aws-sdk-dynamodb 1.117.0 → 1.118.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 9abc2acc269fe7a78efe7d7a07c5dda62d9d536cd853e668e8915c54757c1d35
-  data.tar.gz: e8f9c4151992e99819a331023604e8b389e34170929c24cfedb2d073aac5630c
+  metadata.gz: d8bcda8951d39f0a143d34f76cef98b683e81f941480a590acd34d288dd001cc
+  data.tar.gz: 3d2d2b38b96bd3b81ec60dda7d4f579907af129219823898664fe64254b8356b
 SHA512:
-  metadata.gz: 0c899ccbfc401f2805c5f3f30117e932f216d696946a6e230699b98856bb8870abb68ce5e842b56fb75762d7ab7d52dbd674a1a1357bf6b6720d7335413fb46c
-  data.tar.gz: 4b95f413790d2e913a06ed550c03fab12ccac17a5e36e77f2e888904fea00896674a7069ea483c1dca2da568de3467c7424c7ac81ec0f98bd95879f336d8ef58
+  metadata.gz: 9ce5e271ebac3edfac4c3c55e77e3d41d1353c91c14765e5f13837d24f4d7ac8b7aeaeaa8d735dbe1e011a082f9b85f035d5e62592ee54e5f880b41c510cf7ff
+  data.tar.gz: 75700349e41dd6df0ddbaa6180d1daedf8eb58df4fb4b0b440a192617ebcf5ff728ad3f3f1afaa4c544826135fe3ce69cd499cb172028e6a952baa6381d38f04

data/CHANGELOG.md

@@ -1,6 +1,11 @@
 Unreleased Changes
 ------------------
 
+1.118.0 (2024-07-24)
+------------------
+
+* Feature - DynamoDB doc only update for July
+
 1.117.0 (2024-07-12)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.117.0
+1.118.0

data/lib/aws-sdk-dynamodb/client.rb

@@ -455,7 +455,8 @@ module Aws::DynamoDB
     # stored in DynamoDB, using PartiQL. Each read statement in a
     # `BatchExecuteStatement` must specify an equality condition on all key
     # attributes. This enforces that each `SELECT` statement in a batch
-    # returns at most a single item.
+    # returns at most a single item. For more information, see [Running
+    # batch operations with PartiQL for DynamoDB ][1].
     #
     # <note markdown="1"> The entire batch must consist of either read statements or write
     # statements, you cannot mix both in one batch.
@@ -464,12 +465,13 @@ module Aws::DynamoDB
     #
     # A HTTP 200 response does not mean that all statements in the
     # BatchExecuteStatement succeeded. Error details for individual
-    # statements can be found under the [Error][1] field of the
+    # statements can be found under the [Error][2] field of the
     # `BatchStatementResponse` for each statement.
     #
     #
     #
-    # [1]: https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchStatementResponse.html#DDB-Type-BatchStatementResponse-Error
+    # [1]: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/ql-reference.multiplestatements.batching.html
+    # [2]: https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchStatementResponse.html#DDB-Type-BatchStatementResponse-Error
     #
     # @option params [required, Array<Types::BatchStatementRequest>] :statements
     #   The list of PartiQL statements representing the batch to run.
@@ -857,9 +859,13 @@ module Aws::DynamoDB
     # request with those unprocessed items until all items have been
     # processed.
     #
-    # If *none* of the items can be processed due to insufficient
-    # provisioned throughput on all of the tables in the request, then
-    # `BatchWriteItem` returns a `ProvisionedThroughputExceededException`.
+    # For tables and indexes with provisioned capacity, if none of the items
+    # can be processed due to insufficient provisioned throughput on all of
+    # the tables in the request, then `BatchWriteItem` returns a
+    # `ProvisionedThroughputExceededException`. For all tables and indexes,
+    # if none of the items can be processed due to other throttling
+    # scenarios (such as exceeding partition level limits), then
+    # `BatchWriteItem` returns a `ThrottlingException`.
     #
     # If DynamoDB returns any unprocessed items, you should retry the batch
     # operation on those items. However, *we strongly recommend that you use
@@ -2224,7 +2230,8 @@ module Aws::DynamoDB
     #
     # <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.
+    # the table deletion is complete. For the full list of table states, see
+    # [TableStatus][1].
     #
     #  </note>
     #
@@ -2236,6 +2243,10 @@ module Aws::DynamoDB
     #
     # Use the `DescribeTable` action to check the status of the table.
     #
+    #
+    #
+    # [1]: https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_TableDescription.html#DDB-Type-TableDescription-TableStatus
+    #
     # @option params [required, String] :table_name
     #   The name of the table to delete. You can also provide the Amazon
     #   Resource Name (ARN) of the table in this parameter.
@@ -8365,7 +8376,7 @@ module Aws::DynamoDB
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-dynamodb'
-      context[:gem_version] = '1.117.0'
+      context[:gem_version] = '1.118.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

data/lib/aws-sdk-dynamodb/types.rb

@@ -6946,7 +6946,7 @@ module Aws::DynamoDB
     #
     #
     #
-    #   [1]: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/QueryAndScan.html#Count
+    #   [1]: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Scan.html#Scan.Count
     #   @return [Integer]
     #
     # @!attribute [rw] last_evaluated_key

data/lib/aws-sdk-dynamodb.rb

@@ -54,6 +54,6 @@ require_relative 'aws-sdk-dynamodb/customizations'
 # @!group service
 module Aws::DynamoDB
 
-  GEM_VERSION = '1.117.0'
+  GEM_VERSION = '1.118.0'
 
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-dynamodb
 version: !ruby/object:Gem::Version
-  version: 1.117.0
+  version: 1.118.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2024-07-12 00:00:00.000000000 Z
+date: 2024-07-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core