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.