aws-sdk-dynamodb 1.91.0 → 1.93.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 98e61dbf73f554913ae018ae25f7db16b5116d44c7a1f988e2d6bb919947be32
-  data.tar.gz: 5b009f1b925699bbcd259e07d73ef6ee7d4aabd382ed01518425b4ca8337d6d0
+  metadata.gz: 591f7a25a729e45748300b716eb15b1e7af8312fe995899af2004f0e7f6eb2b2
+  data.tar.gz: 6e85f3e9910e962f4dae28562647d673fee7063bc9aba8d69a2c9e50b1b5a953
 SHA512:
-  metadata.gz: d6dd172ed0a936b88d09579229a17676f42247fa9d5198d8b05e4ca0abef9420fd5714098d44266d19c8244706af27e4e982e4c4f8c9fd6f6bd913df940d1a72
-  data.tar.gz: c4f082ee7f5a66a533b3115331eee83cb950f33b66b512d2ff33be8184c67df7d3385be8757c4a7df0d8cf591e7608df66f75e97edc27bb01736ea5311881321
+  metadata.gz: a5903f7ba1725e52d5c6be5c59c38d41d806cfccbf4a1965bcc85e5a8d1fe3accdd9288164704a583471875ca65b0a5e98053075592a0b2ee6dd3e805f3a406f
+  data.tar.gz: 3e192fc8c4febf19f4555616123433d4c8a65a25121e74b3ed50732ddf6db87342a03ab6500fea0a45d17befcc53d9644767da03e990c6b238bded41ae215578

data/CHANGELOG.md

@@ -1,6 +1,16 @@
 Unreleased Changes
 ------------------
 
+1.93.0 (2023-07-25)
+------------------
+
+* Feature - Documentation updates for DynamoDB
+
+1.92.0 (2023-07-11)
+------------------
+
+* Feature - Code Generated Changes, see `./build_tools` or `aws-sdk-core`'s CHANGELOG.md for details.
+
 1.91.0 (2023-07-06)
 ------------------
 

data/VERSION

@@ -1 +1 @@
-1.91.0
+1.93.0

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

@@ -228,6 +228,10 @@ module Aws::DynamoDB
     #   @option options [Boolean] :endpoint_discovery (false)
     #     When set to `true`, endpoint discovery will be enabled for operations when available.
     #
+    #   @option options [Boolean] :ignore_configured_endpoint_urls
+    #     Setting to true disables use of endpoint URLs provided via environment
+    #     variables and the shared configuration file.
+    #
     #   @option options [Aws::Log::Formatter] :log_formatter (Aws::Log::Formatter.default)
     #     The log formatter.
     #
@@ -5549,18 +5553,30 @@ module Aws::DynamoDB
     # 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 dataset 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.
+    # If the total size of scanned items exceeds the maximum dataset size
+    # limit of 1 MB, the scan completes and results are returned to the
+    # user. The `LastEvaluatedKey` value is also returned and the requestor
+    # can use the `LastEvaluatedKey` to continue the scan in a subsequent
+    # operation. Each scan response also includes number of items that were
+    # scanned (ScannedCount) as part of the request. If using a
+    # `FilterExpression`, a scan result can result in no items meeting the
+    # criteria and the `Count` will result in zero. If you did not use a
+    # `FilterExpression` in the scan request, then `Count` is the same as
+    # `ScannedCount`.
+    #
+    # <note markdown="1"> `Count` and `ScannedCount` only return the count of items specific to
+    # a single scan request and, unless the table is less than 1MB, do not
+    # represent the total number of items in the table.
+    #
+    #  </note>
     #
-    # A single `Scan` operation reads 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 need to paginate
-    # the result set. For more information, see [Paginating the Results][1]
-    # in the *Amazon DynamoDB Developer Guide*.
+    # A single `Scan` operation first reads up to the maximum number of
+    # items set (if using the `Limit` parameter) or a maximum of 1 MB of
+    # data and then applies any filtering to the results if a
+    # `FilterExpression` is provided. If `LastEvaluatedKey` is present in
+    # the response, pagination is required to complete the full table scan.
+    # For more information, see [Paginating the Results][1] in the *Amazon
+    # DynamoDB Developer Guide*.
     #
     # `Scan` operations proceed sequentially; however, for faster
     # performance on a large table or secondary index, applications can
@@ -5568,11 +5584,21 @@ module Aws::DynamoDB
     # `TotalSegments` parameters. For more information, see [Parallel
     # Scan][2] 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`.
+    # By default, a `Scan` uses eventually consistent reads when accessing
+    # the items in a table. Therefore, the results from an eventually
+    # consistent `Scan` may not include the latest item changes at the time
+    # the scan iterates through each item in the table. If you require a
+    # strongly consistent read of each item as the scan iterates through the
+    # items in the table, you can set the `ConsistentRead` parameter to
+    # true. Strong consistency only relates to the consistency of the read
+    # at the item level.
+    #
+    # <note markdown="1"> DynamoDB does not provide snapshot isolation for a scan operation when
+    # the `ConsistentRead` parameter is set to true. Thus, a DynamoDB scan
+    # operation does not guarantee that all reads in a scan see a consistent
+    # snapshot of the table when the scan operation was requested.
+    #
+    #  </note>
     #
     #
     #
@@ -7802,7 +7828,7 @@ module Aws::DynamoDB
         params: params,
         config: config)
       context[:gem_name] = 'aws-sdk-dynamodb'
-      context[:gem_version] = '1.91.0'
+      context[:gem_version] = '1.93.0'
       Seahorse::Client::Request.new(handlers, context)
     end
 

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

@@ -715,7 +715,9 @@ module Aws::DynamoDB
     end
 
     # @!attribute [rw] responses
-    #   The response to each PartiQL statement in the batch.
+    #   The response to each PartiQL statement in the batch. The values of
+    #   the list are ordered according to the ordering of the request
+    #   statements.
     #   @return [Array<Types::BatchStatementResponse>]
     #
     # @!attribute [rw] consumed_capacity
@@ -9075,8 +9077,8 @@ module Aws::DynamoDB
     # @!attribute [rw] return_values_on_condition_check_failure
     #   Use `ReturnValuesOnConditionCheckFailure` to get the item attributes
     #   if the `Update` condition fails. For
-    #   `ReturnValuesOnConditionCheckFailure`, the valid values are: NONE,
-    #   ALL\_OLD, UPDATED\_OLD, ALL\_NEW, UPDATED\_NEW.
+    #   `ReturnValuesOnConditionCheckFailure`, the valid values are: NONE
+    #   and ALL\_OLD.
     #   @return [String]
     #
     # @see http://docs.aws.amazon.com/goto/WebAPI/dynamodb-2012-08-10/Update AWS API Documentation

data/lib/aws-sdk-dynamodb.rb

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

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: aws-sdk-dynamodb
 version: !ruby/object:Gem::Version
-  version: 1.91.0
+  version: 1.93.0
 platform: ruby
 authors:
 - Amazon Web Services
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-07-06 00:00:00.000000000 Z
+date: 2023-07-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: aws-sdk-core