Why expressions matter in pipelines in MongoDB - Visual Breakdown

Concept Flow - Why expressions matter in pipelines

Start with input documents

↓

Apply pipeline stage

↓

Evaluate expressions inside stage

↓

Transform documents based on expressions

↓

Pass transformed documents to next stage

↓

Final output documents

Data flows through pipeline stages where expressions transform documents step-by-step.

Execution Sample

MongoDB

db.collection.aggregate([
  { $match: { status: "A" } },
  { $project: { item: 1, total: { $multiply: ["$price", "$quantity"] } } }
])

Filters documents with status 'A' and calculates total price per item using expressions.

Execution Table

Step	Input Document	Pipeline Stage	Expression Evaluated	Output Document
1	{"item":"apple", "price":2, "quantity":5, "status":"A"}	$match	status == 'A'	{"item":"apple", "price":2, "quantity":5, "status":"A"}
2	{"item":"banana", "price":1, "quantity":10, "status":"B"}	$match	status == 'A'	Filtered out (no output)
3	{"item":"apple", "price":2, "quantity":5, "status":"A"}	$project	total = price * quantity = 2 * 5	{"item":"apple", "total":10}
4	No more documents	End	N/A	Final output: [{"item":"apple", "total":10}]

💡 Pipeline ends after processing all documents; only those matching status 'A' remain with calculated totals.

Variable Tracker

Variable	Start	After Step 1	After Step 3	Final
Document	All documents	{"item":"apple", "price":2, "quantity":5, "status":"A"}	{"item":"apple", "total":10}	[{"item":"apple", "total":10}]

Key Moments - 2 Insights

Why does the banana document disappear after the $match stage?

Because the $match expression filters documents where status equals 'A'. The banana has status 'B', so it is excluded as shown in execution_table row 2.

How is the 'total' field calculated in the $project stage?

The expression multiplies price by quantity (2 * 5 = 10) for each document passing the $match stage, as shown in execution_table row 3.

Visual Quiz - 3 Questions

Look at the execution table, what is the output document after step 3?

A Filtered out (no output)

B {"item":"apple", "price":2, "quantity":5}

C {"item":"apple", "total":10}

D {"item":"banana", "total":10}

💡 Hint

Check the 'Output Document' column in row 3 of the execution_table.

At which step does the pipeline filter out documents with status not equal to 'A'?

A Step 2

B Step 1

C Step 3

D Step 4

💡 Hint

Look at the 'Pipeline Stage' and 'Expression Evaluated' columns in execution_table rows 1 and 2.

If the expression in $project changed to add price and quantity instead of multiply, what would be the total for apple?

A 10

B 7

C 0

D Error

💡 Hint

Refer to variable_tracker and how expressions transform values in the $project stage.

Concept Snapshot

MongoDB pipelines process documents step-by-step.
Expressions inside stages transform data.
$match filters documents by condition.
$project computes new fields using expressions.
Expressions control what data passes and how it changes.

Full Transcript

In MongoDB aggregation pipelines, documents flow through stages. Each stage can use expressions to filter or transform data. For example, $match uses an expression to keep only documents with status 'A'. Then $project uses an expression to calculate a new field 'total' by multiplying price and quantity. Documents not matching the filter are removed early, so only relevant data moves forward. Expressions are important because they define how data changes at each step, shaping the final output.

Practice

1. What is the main reason expressions are important in MongoDB aggregation pipelines?

easy

A. They backup the database during aggregation.

B. They create new collections automatically.

C. They replace the need for indexes.

D. They allow you to calculate and transform data within pipeline stages.

Solution

1. Step 1: Understand the role of expressions in pipelines

   Expressions let you perform calculations and data transformations inside stages like $project and $group.

2. Step 2: Compare other options

   Options A, B, and C describe unrelated features not handled by expressions.

3. Final Answer:

   They allow you to calculate and transform data within pipeline stages. -> Option D

4. Quick Check:

   Expressions = Data transformation [OK]

Hint: Expressions transform data inside stages like $project [OK]

Common Mistakes:

• Thinking expressions create collections
• Confusing expressions with indexing
• Assuming expressions handle backups

2. Which of the following is the correct syntax to use an expression in a $project stage to add two fields price and tax?

easy

A. { $project: { total: { $add: ["$price", "$tax"] } } }

B. { $project: { total: $add(price, tax) } }

C. { $project: { total: { add: [price, tax] } } }

D. { $project: { total: { $sum: "$price" + "$tax" } } }

Solution

1. Step 1: Identify correct expression syntax

   The $add operator requires an array of field references with $ prefix inside an object.

2. Step 2: Check each option

   { $project: { total: { $add: ["$price", "$tax"] } } } correctly uses $add with an array of "$price" and "$tax". Others misuse syntax or operators.

3. Final Answer:

   { $project: { total: { $add: ["$price", "$tax"] } } } -> Option A

4. Quick Check:

   $add needs array with $field names [OK]

Hint: Use $add with array of "$field" names in $project [OK]

Common Mistakes:

• Omitting $ before field names
• Using parentheses instead of array for $add
• Confusing $add with $sum operator

3. Given the pipeline stage:

{ $project: { discountedPrice: { $multiply: ["$price", 0.9] } } }

What will be the output for a document { price: 100 }?

medium

A. { discountedPrice: 10 }

B. { discountedPrice: 90 }

C. { discountedPrice: 100 }

D. { discountedPrice: 0.9 }

Solution

1. Step 1: Understand $multiply expression

   $multiply multiplies the values in the array. Here, price (100) * 0.9 = 90.

2. Step 2: Apply to given document

   Input price is 100, so discountedPrice = 100 * 0.9 = 90.

3. Final Answer:

   { discountedPrice: 90 } -> Option B

4. Quick Check:

   100 * 0.9 = 90 [OK]

Hint: Multiply fields with constants using $multiply [OK]

Common Mistakes:

• Confusing multiplication with subtraction
• Using 0.9 as a field instead of a number
• Expecting original price unchanged

4. Identify the error in this pipeline stage:

{ $project: { total: { $add: "$price", "$tax" } } }

medium

A. The $project stage cannot use $add operator.

B. Field names should not have $ prefix inside $add.

C. The $add operator requires an array of expressions, not separate arguments.

D. The syntax is correct; no error.

Solution

1. Step 1: Review $add operator syntax

   $add expects a single array argument containing expressions, not multiple separate arguments.

2. Step 2: Analyze given code

   The code passes "$price" and "$tax" as separate arguments instead of inside an array.

3. Final Answer:

   The $add operator requires an array of expressions, not separate arguments. -> Option C

4. Quick Check:

   $add needs array input [OK]

Hint: Always pass array to $add, not separate arguments [OK]

Common Mistakes:

• Passing multiple arguments instead of array
• Removing $ from field names inside expressions
• Assuming $project can't use expressions

5. You want to create a pipeline that groups sales by product and calculates the average revenue per sale, but only for sales where quantity is greater than 5. Which expression usage is correct inside the pipeline?

hard

A. { $match: { quantity: { $gt: 5 } } }, { $group: { _id: "$product", avgRevenue: { $avg: { $multiply: ["$price", "$quantity"] } } } }

B. { $group: { _id: "$product", avgRevenue: { $avg: { $multiply: ["$price", "$quantity"] } } } }, { $match: { quantity: { $gt: 5 } } }

C. { $match: { quantity: { $lt: 5 } } }, { $group: { _id: "$product", avgRevenue: { $avg: "$price" } } }

D. { $group: { _id: "$product", avgRevenue: { $sum: "$price" } } }, { $match: { quantity: { $gt: 5 } } }

Solution

1. Step 1: Filter sales with $match before grouping

   To include only sales with quantity > 5, $match must come before $group.

2. Step 2: Use $avg with $multiply expression inside $group

   Calculate revenue per sale as price * quantity, then average it per product.

3. Step 3: Check options

   { $match: { quantity: { $gt: 5 } } }, { $group: { _id: "$product", avgRevenue: { $avg: { $multiply: ["$price", "$quantity"] } } } } correctly orders stages and uses expressions. Others have wrong order or wrong operators.

4. Final Answer:

   { $match: { quantity: { $gt: 5 } } }, { $group: { _id: "$product", avgRevenue: { $avg: { $multiply: ["$price", "$quantity"] } } } } -> Option A

5. Quick Check:

   Filter then group with $avg of $multiply [OK]

Hint: Filter first with $match, then use expressions in $group [OK]

Common Mistakes:

• Placing $match after $group
• Using $sum instead of $avg for average
• Filtering with wrong comparison operator