aws-sdk-dynamodb 1.92.0 → 1.93.0

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 28be9d53d076526f477ce1a55119335c4094942384ce310b18851e7f8849ff3d
4
- data.tar.gz: 4d368d2eb8fffe18528ebb3e5ddf3a59bb9284d3d930dc50d9f6ae7a3eb29c5b
3
+ metadata.gz: 591f7a25a729e45748300b716eb15b1e7af8312fe995899af2004f0e7f6eb2b2
4
+ data.tar.gz: 6e85f3e9910e962f4dae28562647d673fee7063bc9aba8d69a2c9e50b1b5a953
5
5
  SHA512:
6
- metadata.gz: 4f2bfe0e4c77f50c8579a300e49d97bcef1f42a489de5314e9f4da855cb6ba636d43a6ffedfa580f589e127f7c0c640910390bbb08c7c8c79f88b305a994c33a
7
- data.tar.gz: cd991b09a3b012ac7038c48fef6f23d43e265a9aee47b85cd2ee976546193129edf4a2f9b0696a5dec2f02ef166523bed5d5f8848a99e0a23e5f69d58dff4661
6
+ metadata.gz: a5903f7ba1725e52d5c6be5c59c38d41d806cfccbf4a1965bcc85e5a8d1fe3accdd9288164704a583471875ca65b0a5e98053075592a0b2ee6dd3e805f3a406f
7
+ data.tar.gz: 3e192fc8c4febf19f4555616123433d4c8a65a25121e74b3ed50732ddf6db87342a03ab6500fea0a45d17befcc53d9644767da03e990c6b238bded41ae215578
data/CHANGELOG.md CHANGED
@@ -1,6 +1,11 @@
1
1
  Unreleased Changes
2
2
  ------------------
3
3
 
4
+ 1.93.0 (2023-07-25)
5
+ ------------------
6
+
7
+ * Feature - Documentation updates for DynamoDB
8
+
4
9
  1.92.0 (2023-07-11)
5
10
  ------------------
6
11
 
data/VERSION CHANGED
@@ -1 +1 @@
1
- 1.92.0
1
+ 1.93.0
@@ -5553,18 +5553,30 @@ module Aws::DynamoDB
5553
5553
  # accessing every item in a table or a secondary index. To have DynamoDB
5554
5554
  # return fewer items, you can provide a `FilterExpression` operation.
5555
5555
  #
5556
- # If the total number of scanned items exceeds the maximum dataset size
5557
- # limit of 1 MB, the scan stops and results are returned to the user as
5558
- # a `LastEvaluatedKey` value to continue the scan in a subsequent
5559
- # operation. The results also include the number of items exceeding the
5560
- # limit. A scan can result in no table data meeting the filter criteria.
5561
- #
5562
- # A single `Scan` operation reads up to the maximum number of items set
5563
- # (if using the `Limit` parameter) or a maximum of 1 MB of data and then
5564
- # apply any filtering to the results using `FilterExpression`. If
5565
- # `LastEvaluatedKey` is present in the response, you need to paginate
5566
- # the result set. For more information, see [Paginating the Results][1]
5567
- # in the *Amazon DynamoDB Developer Guide*.
5556
+ # If the total size of scanned items exceeds the maximum dataset size
5557
+ # limit of 1 MB, the scan completes and results are returned to the
5558
+ # user. The `LastEvaluatedKey` value is also returned and the requestor
5559
+ # can use the `LastEvaluatedKey` to continue the scan in a subsequent
5560
+ # operation. Each scan response also includes number of items that were
5561
+ # scanned (ScannedCount) as part of the request. If using a
5562
+ # `FilterExpression`, a scan result can result in no items meeting the
5563
+ # criteria and the `Count` will result in zero. If you did not use a
5564
+ # `FilterExpression` in the scan request, then `Count` is the same as
5565
+ # `ScannedCount`.
5566
+ #
5567
+ # <note markdown="1"> `Count` and `ScannedCount` only return the count of items specific to
5568
+ # a single scan request and, unless the table is less than 1MB, do not
5569
+ # represent the total number of items in the table.
5570
+ #
5571
+ # </note>
5572
+ #
5573
+ # A single `Scan` operation first reads up to the maximum number of
5574
+ # items set (if using the `Limit` parameter) or a maximum of 1 MB of
5575
+ # data and then applies any filtering to the results if a
5576
+ # `FilterExpression` is provided. If `LastEvaluatedKey` is present in
5577
+ # the response, pagination is required to complete the full table scan.
5578
+ # For more information, see [Paginating the Results][1] in the *Amazon
5579
+ # DynamoDB Developer Guide*.
5568
5580
  #
5569
5581
  # `Scan` operations proceed sequentially; however, for faster
5570
5582
  # performance on a large table or secondary index, applications can
@@ -5572,11 +5584,21 @@ module Aws::DynamoDB
5572
5584
  # `TotalSegments` parameters. For more information, see [Parallel
5573
5585
  # Scan][2] in the *Amazon DynamoDB Developer Guide*.
5574
5586
  #
5575
- # `Scan` uses eventually consistent reads when accessing the data in a
5576
- # table; therefore, the result set might not include the changes to data
5577
- # in the table immediately before the operation began. If you need a
5578
- # consistent copy of the data, as of the time that the `Scan` begins,
5579
- # you can set the `ConsistentRead` parameter to `true`.
5587
+ # By default, a `Scan` uses eventually consistent reads when accessing
5588
+ # the items in a table. Therefore, the results from an eventually
5589
+ # consistent `Scan` may not include the latest item changes at the time
5590
+ # the scan iterates through each item in the table. If you require a
5591
+ # strongly consistent read of each item as the scan iterates through the
5592
+ # items in the table, you can set the `ConsistentRead` parameter to
5593
+ # true. Strong consistency only relates to the consistency of the read
5594
+ # at the item level.
5595
+ #
5596
+ # <note markdown="1"> DynamoDB does not provide snapshot isolation for a scan operation when
5597
+ # the `ConsistentRead` parameter is set to true. Thus, a DynamoDB scan
5598
+ # operation does not guarantee that all reads in a scan see a consistent
5599
+ # snapshot of the table when the scan operation was requested.
5600
+ #
5601
+ # </note>
5580
5602
  #
5581
5603
  #
5582
5604
  #
@@ -7806,7 +7828,7 @@ module Aws::DynamoDB
7806
7828
  params: params,
7807
7829
  config: config)
7808
7830
  context[:gem_name] = 'aws-sdk-dynamodb'
7809
- context[:gem_version] = '1.92.0'
7831
+ context[:gem_version] = '1.93.0'
7810
7832
  Seahorse::Client::Request.new(handlers, context)
7811
7833
  end
7812
7834
 
@@ -715,7 +715,9 @@ module Aws::DynamoDB
715
715
  end
716
716
 
717
717
  # @!attribute [rw] responses
718
- # The response to each PartiQL statement in the batch.
718
+ # The response to each PartiQL statement in the batch. The values of
719
+ # the list are ordered according to the ordering of the request
720
+ # statements.
719
721
  # @return [Array<Types::BatchStatementResponse>]
720
722
  #
721
723
  # @!attribute [rw] consumed_capacity
@@ -9075,8 +9077,8 @@ module Aws::DynamoDB
9075
9077
  # @!attribute [rw] return_values_on_condition_check_failure
9076
9078
  # Use `ReturnValuesOnConditionCheckFailure` to get the item attributes
9077
9079
  # if the `Update` condition fails. For
9078
- # `ReturnValuesOnConditionCheckFailure`, the valid values are: NONE,
9079
- # ALL\_OLD, UPDATED\_OLD, ALL\_NEW, UPDATED\_NEW.
9080
+ # `ReturnValuesOnConditionCheckFailure`, the valid values are: NONE
9081
+ # and ALL\_OLD.
9080
9082
  # @return [String]
9081
9083
  #
9082
9084
  # @see http://docs.aws.amazon.com/goto/WebAPI/dynamodb-2012-08-10/Update AWS API Documentation
@@ -54,6 +54,6 @@ require_relative 'aws-sdk-dynamodb/customizations'
54
54
  # @!group service
55
55
  module Aws::DynamoDB
56
56
 
57
- GEM_VERSION = '1.92.0'
57
+ GEM_VERSION = '1.93.0'
58
58
 
59
59
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aws-sdk-dynamodb
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.92.0
4
+ version: 1.93.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Amazon Web Services
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2023-07-11 00:00:00.000000000 Z
11
+ date: 2023-07-25 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: aws-sdk-core