The Scan operation returns one or more items and item attributes by
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 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.
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.
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 in the Amazon DynamoDB Developer Guide.
Scan operations proceed sequentially; however, for faster performance on
a large table or secondary index, applications can request a parallel Scan
operation by providing the Segment and TotalSegments
parameters. For more information, see Parallel
Scan in the Amazon DynamoDB Developer Guide.
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.
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.
Example
Use a bare-bones client and the command you need to make an API call.
Your request rate is too high. The Amazon Web Services SDKs for DynamoDB
automatically retry requests that receive this exception. Your request is eventually
successful, unless your retry queue is too large to finish. Reduce the frequency of
requests and use exponential backoff. For more information, go to Error Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
Base exception class for all service exceptions from DynamoDB service.
Example
To scan a table
// This example scans the entire Music table, and then narrows the results to songs by the artist "No One You Know". For each item, only the album title and song title are returned. constinput = { "ExpressionAttributeNames": { "#AT":"AlbumTitle", "#ST":"SongTitle" }, "ExpressionAttributeValues": { ":a": { "S":"No One You Know" } }, "FilterExpression":"Artist = :a", "ProjectionExpression":"#ST, #AT", "TableName":"Music" }; constcommand = newScanCommand(input); constresponse = awaitclient.send(command); /* response == { "ConsumedCapacity": {}, "Count": 2, "Items": [ { "AlbumTitle": { "S": "Somewhat Famous" }, "SongTitle": { "S": "Call Me Today" } }, { "AlbumTitle": { "S": "Blue Sky Blues" }, "SongTitle": { "S": "Scared of My Shadow" } } ], "ScannedCount": 3 } */ // example id: to-scan-a-table-1475883652470
The
Scan
operation returns one or more items and item attributes by accessing every item in a table or a secondary index. To have DynamoDB return fewer items, you can provide aFilterExpression
operation.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 theLastEvaluatedKey
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 aFilterExpression
, a scan result can result in no items meeting the criteria and theCount
will result in zero. If you did not use aFilterExpression
in the scan request, thenCount
is the same asScannedCount
.Count
andScannedCount
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.A single
Scan
operation first reads up to the maximum number of items set (if using theLimit
parameter) or a maximum of 1 MB of data and then applies any filtering to the results if aFilterExpression
is provided. IfLastEvaluatedKey
is present in the response, pagination is required to complete the full table scan. For more information, see Paginating the Results in the Amazon DynamoDB Developer Guide.Scan
operations proceed sequentially; however, for faster performance on a large table or secondary index, applications can request a parallelScan
operation by providing theSegment
andTotalSegments
parameters. For more information, see Parallel Scan in the Amazon DynamoDB Developer Guide.By default, a
Scan
uses eventually consistent reads when accessing the items in a table. Therefore, the results from an eventually consistentScan
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 theConsistentRead
parameter to true. Strong consistency only relates to the consistency of the read at the item level.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.Example
Use a bare-bones client and the command you need to make an API call.
Param
ScanCommandInput
Returns
ScanCommandOutput
See
input
shape.response
shape.config
shape.Throws
InternalServerError (server fault)
An error occurred on the server side.
Throws
InvalidEndpointException (client fault)
Throws
ProvisionedThroughputExceededException (client fault)
Your request rate is too high. The Amazon Web Services SDKs for DynamoDB automatically retry requests that receive this exception. Your request is eventually successful, unless your retry queue is too large to finish. Reduce the frequency of requests and use exponential backoff. For more information, go to Error Retries and Exponential Backoff in the Amazon DynamoDB Developer Guide.
Throws
RequestLimitExceeded (client fault)
Throughput exceeds the current throughput quota for your account. Please contact Amazon Web Services Support to request a quota increase.
Throws
ResourceNotFoundException (client fault)
The operation tried to access a nonexistent table or index. The resource might not be specified correctly, or its status might not be
ACTIVE
.Throws
DynamoDBServiceException
Base exception class for all service exceptions from DynamoDB service.
Example
To scan a table