Why expressions matter in pipelines in MongoDB - See It in Action

Why expressions matter in pipelines

📖 Scenario: You work for a small online bookstore. You have a collection of books documents in MongoDB. Each book has fields like title, author, price, and copies_sold. You want to analyze sales data using aggregation pipelines.

🎯 Goal: Build a MongoDB aggregation pipeline step-by-step that uses expressions to calculate total revenue per book and filter books with revenue above a certain amount.

📋 What You'll Learn

Create a books collection with exact documents

Add a variable for minimum revenue threshold

Use $addFields with an expression to calculate revenue

Use $match to filter books by revenue

💡 Why This Matters

🌍 Real World

Online stores and data analysts use aggregation pipelines to calculate sales metrics and filter products dynamically.

💼 Career

Understanding expressions in MongoDB pipelines is essential for backend developers and data engineers working with NoSQL databases.

1

DATA SETUP: Create the books collection with documents

Create a variable called books that is a list of three documents exactly as follows: {"title": "Learn MongoDB", "author": "Alice", "price": 30, "copies_sold": 100}, {"title": "Advanced MongoDB", "author": "Bob", "price": 45, "copies_sold": 50}, and {"title": "MongoDB for Beginners", "author": "Carol", "price": 25, "copies_sold": 200}.

MongoDB

books = [
    # Your code here
]

Hint

Use a Python list with dictionaries for each book document.

2

CONFIGURATION: Set a minimum revenue threshold

Create a variable called min_revenue and set it to 3000.

MongoDB

books = [
    {"title": "Learn MongoDB", "author": "Alice", "price": 30, "copies_sold": 100},
    {"title": "Advanced MongoDB", "author": "Bob", "price": 45, "copies_sold": 50},
    {"title": "MongoDB for Beginners", "author": "Carol", "price": 25, "copies_sold": 200}
]
# Your code here

Hint

Just assign the number 3000 to min_revenue.

3

CORE LOGIC: Use $addFields to calculate revenue per book

Create a variable called pipeline that is a list with one stage: { "$addFields": { "revenue": { "$multiply": ["$price", "$copies_sold"] } }}.

MongoDB

books = [
    {"title": "Learn MongoDB", "author": "Alice", "price": 30, "copies_sold": 100},
    {"title": "Advanced MongoDB", "author": "Bob", "price": 45, "copies_sold": 50},
    {"title": "MongoDB for Beginners", "author": "Carol", "price": 25, "copies_sold": 200}
]
min_revenue = 3000
# Your code here

Hint

Use $multiply inside $addFields to create a new field revenue.

4

COMPLETION: Add a $match stage to filter books by revenue

Add a second stage to the pipeline list: { "$match": { "revenue": { "$gt": min_revenue } } }.

MongoDB

books = [
    {"title": "Learn MongoDB", "author": "Alice", "price": 30, "copies_sold": 100},
    {"title": "Advanced MongoDB", "author": "Bob", "price": 45, "copies_sold": 50},
    {"title": "MongoDB for Beginners", "author": "Carol", "price": 25, "copies_sold": 200}
]
min_revenue = 3000
pipeline = [
    { "$addFields": { "revenue": { "$multiply": ["$price", "$copies_sold"] } } }
]
# Your code here

Hint

Add a $match stage after $addFields to filter books with revenue greater than min_revenue.

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