Basic scan operation in DynamoDB

Introduction

A basic scan operation reads every item in a DynamoDB table. It helps you see all the data stored without any filters.

You want to get all the records from a small table to see what data it holds.

You need to export all data from a table for backup or analysis.

You want to quickly check the contents of a table during development.

You want to count how many items are in a table without conditions.

You want to retrieve all items before applying filters in your application code.

Syntax

DynamoDB

aws dynamodb scan \
  --table-name TableName \
  [--filter-expression FilterExpression] \
  [--projection-expression Attributes] \
  [--limit Number]

The Scan command reads every item in the table.

You can add filters to reduce returned items, but the scan still reads all data internally.

Examples

Scan the entire 'Music' table and return all items.

DynamoDB

aws dynamodb scan --table-name Music

Scan 'Music' table but only return items where Artist is 'No One You Know'.

DynamoDB

aws dynamodb scan --table-name Music --filter-expression "Artist = :artist" --expression-attribute-values '{":artist":{"S":"No One You Know"}}'

Scan 'Music' table but return only the SongTitle and AlbumTitle attributes.

DynamoDB

aws dynamodb scan --table-name Music --projection-expression "SongTitle, AlbumTitle"

Sample Program

This command scans the entire 'Books' table and returns all items stored in it.

DynamoDB

aws dynamodb scan --table-name Books

Important Notes

Scan reads every item, so it can be slow and costly on large tables.

Use FilterExpression to reduce returned data but scan still reads all items.

For large tables, consider using queries or indexes for better performance.

Summary

Scan reads all items in a DynamoDB table.

It is simple but can be slow for big tables.

Use filters to limit returned data but scan still reads everything internally.

Practice

1. What does the scan operation do in DynamoDB?

easy

A. Reads all items in a table

B. Reads only one item by key

C. Deletes items from a table

D. Updates items in a table

Solution

1. Step 1: Understand the scan operation

   The scan operation reads every item in the DynamoDB table without filtering by key.

2. Step 2: Compare with other operations

   Unlike get or query, scan reads all items, not just specific keys.

3. Final Answer:

   Reads all items in a table -> Option A

4. Quick Check:

   Scan = Reads all items [OK]

Hint: Scan reads entire table, not just keys [OK]

Common Mistakes:

• Confusing scan with get or query
• Thinking scan deletes or updates data
• Assuming scan reads only filtered items

2. Which of the following is the correct syntax to perform a scan operation using AWS SDK for JavaScript v3?

easy

A. const data = await client.get({ TableName: 'MyTable' });

B. const data = await client.query({ TableName: 'MyTable' });

C. const data = await client.scan({ TableName: 'MyTable' });

D. const data = await client.delete({ TableName: 'MyTable' });

Solution

1. Step 1: Identify scan method usage

   The scan method is called on the DynamoDB client with parameters including TableName.

2. Step 2: Check other methods

   Get, query, and delete are different operations and do not perform scan.

3. Final Answer:

   const data = await client.scan({ TableName: 'MyTable' }); -> Option C

4. Quick Check:

   Scan syntax uses client.scan() [OK]

Hint: Scan uses client.scan() with TableName [OK]

Common Mistakes:

• Using get or query instead of scan
• Missing await keyword
• Wrong method names like delete

3. Given a DynamoDB table with 3 items: {id:1, name:'A'}, {id:2, name:'B'}, {id:3, name:'C'}, what will the scan operation return?

medium

A. [{id:1, name:'A'}, {id:2, name:'B'}, {id:3, name:'C'}]

B. Error: No items found

C. []

D. [{id:1, name:'A'}]

Solution

1. Step 1: Understand scan returns all items

   Scan reads every item in the table, so all 3 items will be returned.

2. Step 2: Check options for completeness

   Only [{id:1, name:'A'}, {id:2, name:'B'}, {id:3, name:'C'}] lists all 3 items; others are incomplete or errors.

3. Final Answer:

   [{id:1, name:'A'}, {id:2, name:'B'}, {id:3, name:'C'}] -> Option A

4. Quick Check:

   Scan returns all items [OK]

Hint: Scan returns full table items list [OK]

Common Mistakes:

• Expecting scan to return only one item
• Thinking scan returns empty if no filter
• Confusing scan with query results

4. You wrote this code to scan a DynamoDB table but get no results:

const params = { TableName: 'MyTable', FilterExpression: 'age > :val', ExpressionAttributeValues: { ':val': 30 } };
const data = await client.scan(params);

What is the likely problem?

medium

A. TableName is missing in params

B. FilterExpression syntax is incorrect, causing scan to fail

C. Scan does not support FilterExpression

D. FilterExpression is applied after scan reads all items, so no items match age > 30

Solution

1. Step 1: Understand FilterExpression in scan

   FilterExpression filters results after scanning all items; if no items match, result is empty.

2. Step 2: Check syntax and params

   Syntax is correct, TableName is present, and scan supports FilterExpression.

3. Final Answer:

   FilterExpression is applied after scan reads all items, so no items match age > 30 -> Option D

4. Quick Check:

   FilterExpression filters after scan [OK]

Hint: FilterExpression filters after scan reads all items [OK]

Common Mistakes:

• Thinking FilterExpression prevents scanning items
• Assuming scan fails with FilterExpression
• Missing TableName parameter

5. You want to scan a large DynamoDB table but only retrieve items where status is 'active'. Which approach is best to reduce data returned and improve performance?

hard

A. Use scan with FilterExpression 'status = :s' and ExpressionAttributeValues { ':s': 'active' }

B. Use query operation with status as partition key

C. Use scan without filters and filter results in application code

D. Use scan with ProjectionExpression to get only 'status' attribute

Solution

1. Step 1: Understand scan vs query

   Scan reads entire table; query reads items by key, more efficient for filtering.

2. Step 2: Check if status can be partition key

   If status is partition key, query can efficiently get only 'active' items without scanning all.

3. Step 3: Evaluate other options

   FilterExpression filters after scan, so less efficient; filtering in app wastes bandwidth; ProjectionExpression only limits attributes, not items.

4. Final Answer:

   Use query operation with status as partition key -> Option B

5. Quick Check:

   Query with key filters efficiently [OK]

Hint: Query by key is faster than scan with filters [OK]

Common Mistakes:

• Relying on scan with filters for large tables
• Filtering data in application instead of query
• Confusing ProjectionExpression with filtering items