Filter expressions in DynamoDB - Step-by-Step Execution

Concept Flow - Filter expressions

Start Scan or Query

↓

Apply Filter Expression

↓

Include Item

↓

Return Filtered Results

↓

End

The database scans or queries items, applies the filter expression to each, includes items that match, excludes others, then returns the filtered results.

Execution Sample

DynamoDB

Scan table 'Books' with FilterExpression: Author = 'Alice'

This scan returns only items where the Author attribute equals 'Alice'.

Execution Table

Step	Item	Author Attribute	Filter Condition (Author = 'Alice')	Include in Result?
1	{BookID: 1, Author: 'Alice', Title: 'A1'}	Alice	True	Yes
2	{BookID: 2, Author: 'Bob', Title: 'B1'}	Bob	False	No
3	{BookID: 3, Author: 'Alice', Title: 'A2'}	Alice	True	Yes
4	{BookID: 4, Author: 'Carol', Title: 'C1'}	Carol	False	No
5	{BookID: 5, Author: 'Alice', Title: 'A3'}	Alice	True	Yes
6	No more items	-	-	-

💡 All items scanned; only those with Author = 'Alice' included in results.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	Final
Current Item	None	{BookID:1,...}	{BookID:2,...}	{BookID:3,...}	{BookID:4,...}	{BookID:5,...}	None
Include in Result	N/A	Yes	No	Yes	No	Yes	N/A

Key Moments - 2 Insights

Why are some items scanned but not included in the results?

Because the filter expression only includes items where Author = 'Alice'. Items with other authors fail the condition and are excluded, as shown in steps 2 and 4 of the execution_table.

Does the filter expression reduce the number of items read from the table?

No, the filter expression applies after reading items. All items are scanned, but only matching items are returned. This is why all items appear in the execution_table steps.

Visual Quiz - 3 Questions

Look at the execution_table, what is the Include in Result value at Step 4?

A No

B True

C Yes

D False

💡 Hint

Check the 'Include in Result?' column at Step 4 in the execution_table.

At which step does the filter condition first evaluate to False?

A Step 1

B Step 3

C Step 2

D Step 5

💡 Hint

Look at the 'Filter Condition' column in the execution_table to find the first False.

If the filter expression changed to Author = 'Bob', how would the Include in Result column change?

A All steps would be Yes

B Only Step 2 would be Yes, others No

C All steps would be No

D Steps 1, 3, and 5 would be Yes

💡 Hint

Refer to the 'Author Attribute' column and match with the new filter condition.

Concept Snapshot

Filter expressions in DynamoDB apply after reading items.
They test each item against a condition.
Only items passing the filter are returned.
All items are scanned or queried first.
Filter does not reduce read capacity usage.
Syntax example: FilterExpression = 'Author = :val'.

Full Transcript

In DynamoDB, filter expressions are conditions applied after scanning or querying items. The database reads all items matching the query or scan, then tests each item against the filter expression. Items that meet the condition are included in the results; others are excluded. For example, scanning a 'Books' table with FilterExpression 'Author = Alice' returns only books authored by Alice. The execution table shows each item scanned, the author attribute, whether the filter condition is true or false, and if the item is included. This helps understand that filter expressions do not reduce the number of items read, only the items returned. Key moments include understanding why some items are excluded and that filter expressions apply after reading. The visual quiz tests knowledge of specific steps and how changing the filter affects results.

Practice

1. What is the main purpose of a FilterExpression in a DynamoDB scan or query?

easy

A. To return only items that meet specific conditions after reading all data

B. To reduce the size of the table permanently

C. To speed up the write operations

D. To create new indexes automatically

Solution

1. Step 1: Understand what FilterExpression does

   A FilterExpression is used to specify conditions that items must meet to be returned after the scan or query reads the data.

2. Step 2: Differentiate from other operations

   It does not change the table or speed up writes; it only filters results after reading.

3. Final Answer:

   To return only items that meet specific conditions after reading all data -> Option A

4. Quick Check:

   FilterExpression filters results after reading [OK]

Hint: FilterExpression filters results after reading data [OK]

Common Mistakes:

• Thinking FilterExpression reduces read capacity usage
• Confusing FilterExpression with key condition
• Assuming it changes the table data

2. Which of the following is the correct syntax for a FilterExpression to find items where attribute status equals 'active' in DynamoDB?

easy

A. FilterExpression: "status = 'active'"

B. FilterExpression: "status == 'active'"

C. FilterExpression: "status equals 'active'"

D. FilterExpression: "status === 'active'"

Solution

1. Step 1: Recall DynamoDB FilterExpression syntax

   DynamoDB uses single equals sign (=) for equality in FilterExpressions.

2. Step 2: Check each option

   FilterExpression: "status = 'active'" uses correct syntax. The other options use invalid operators (==, equals, ===) or keywords.

3. Final Answer:

   FilterExpression: "status = 'active'" -> Option A

4. Quick Check:

   Use single equals (=) for equality in FilterExpression [OK]

Hint: Use single '=' for equality in FilterExpression [OK]

Common Mistakes:

• Using double or triple equals (==, ===)
• Writing 'equals' as a word
• Using incorrect operators

3. Given a DynamoDB table with items having attribute age, what will be the result of this scan with FilterExpression age < 30 if the table has ages 25, 30, 35, and 40?

medium

A. Items with ages 25 and 30

B. Items with ages 25 only

C. Items with ages 30, 35, and 40

D. Items with ages 35 and 40

Solution

1. Step 1: Understand the FilterExpression condition

   The condition is age < 30, meaning only items with age less than 30 pass the filter.

2. Step 2: Check which ages satisfy the condition

   From the list (25, 30, 35, 40), only 25 is less than 30.

3. Final Answer:

   Items with ages 25 only -> Option B

4. Quick Check:

   age < 30 means less than 30 [OK]

Hint: Remember < means strictly less than [OK]

Common Mistakes:

• Including age 30 when condition is less than 30
• Confusing < with <= operator
• Assuming filter changes data in table

4. You wrote this FilterExpression: contains(name, 'John') but it returns no results even though some items have 'John' in their name. What is the likely mistake?

medium

A. Using contains() instead of equals()

B. Not using ExpressionAttributeNames for reserved words

C. FilterExpression is case-sensitive and 'John' does not match 'john'

D. FilterExpression must be in uppercase

Solution

1. Step 1: Understand contains() behavior

   contains() checks if the attribute contains the exact substring, including case.

2. Step 2: Consider case sensitivity

   If the data has 'john' lowercase but the filter uses 'John' with uppercase J, no match occurs.

3. Step 3: Check other choices

   Using equals() instead of contains() is not the issue since contains() is appropriate for substrings; reserved words would cause a different error; FilterExpressions are not required to be uppercase.

4. Final Answer:

   FilterExpression is case-sensitive and 'John' does not match 'john' -> Option C

5. Quick Check:

   contains() is case-sensitive [OK]

Hint: Remember contains() is case-sensitive [OK]

Common Mistakes:

• Ignoring case sensitivity in contains()
• Not using ExpressionAttributeNames when needed
• Assuming contains() works like equals()

5. You want to scan a DynamoDB table to find items where score is greater than 50 and status is 'active'. Which FilterExpression correctly applies both conditions?

hard

A. FilterExpression: "score > 50, status = 'active'"

B. FilterExpression: "score > 50 OR status = 'active'"

C. FilterExpression: "score > 50 && status == 'active'"

D. FilterExpression: "score > 50 AND status = 'active'"

Solution

1. Step 1: Understand logical operators in FilterExpression

   DynamoDB uses uppercase AND and OR for combining conditions.

2. Step 2: Check each option's syntax

   FilterExpression: "score > 50 AND status = 'active'" uses correct syntax with AND and single equals. FilterExpression: "score > 50 OR status = 'active'" uses OR which is incorrect for both conditions. FilterExpression: "score > 50, status = 'active'" uses comma which is invalid. FilterExpression: "score > 50 && status == 'active'" uses && and double equals which are invalid.

3. Final Answer:

   FilterExpression: "score > 50 AND status = 'active'" -> Option D

4. Quick Check:

   Use AND in uppercase and single '=' for equality [OK]

Hint: Use uppercase AND and single '=' in FilterExpression [OK]

Common Mistakes:

• Using OR instead of AND for both conditions
• Using commas or && instead of AND
• Using double equals (==) instead of single equals (=)