$lookup with pipeline (advanced join) in MongoDB - Time & Space Complexity

Time Complexity: $lookup with pipeline (advanced join)

O(n x m)

Understanding Time Complexity

When using $lookup with a pipeline in MongoDB, we want to understand how the time it takes grows as the data gets bigger.

We ask: How does the number of operations change when joining collections with a pipeline?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

db.orders.aggregate([
  {
    $lookup: {
      from: "products",
      let: { order_item: "$item" },
      pipeline: [
        { $match: { $expr: { $eq: ["$name", "$$order_item"] } } },
        { $project: { price: 1, _id: 0 } }
      ],
      as: "productDetails"
    }
  }
])

This code joins the orders collection with products using a pipeline to match and project product details for each order item.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: For each document in orders, the pipeline runs a $match on products.
• How many times: Once per orders document, so the number of orders documents times the cost of matching in products.

How Execution Grows With Input

As the number of orders grows, the pipeline runs more times. Each run searches products for matches.

Input Size (orders)	Approx. Operations
10	10 x cost of matching in products
100	100 x cost of matching in products
1000	1000 x cost of matching in products

Pattern observation: The total work grows roughly in direct proportion to the number of orders documents.

Final Time Complexity

Time Complexity: O(n x m)

This means the time grows with the number of orders (n) times the number of products (m) scanned per lookup.

Common Mistake

[X] Wrong: "The $lookup with pipeline runs just once regardless of input size."

[OK] Correct: Actually, the pipeline runs once for each orders document, so the work multiplies with input size.

Interview Connect

Understanding how $lookup with pipelines scales helps you explain data joining costs clearly, a useful skill when discussing database performance.

Self-Check

What if we added an index on the products.name field used in $match? How would the time complexity change?

Practice

1. What is the main purpose of using $lookup with a pipeline in MongoDB?

easy

A. To create indexes on joined collections automatically

B. To update documents in the joined collection

C. To perform advanced joins with filtering and transformations on the joined data

D. To delete documents from multiple collections at once

Solution

1. Step 1: Understand $lookup basic function

   $lookup is used to join documents from another collection into the current one.

2. Step 2: Role of pipeline in $lookup

   Using a pipeline allows filtering and transforming the joined documents before adding them.

3. Final Answer:

   To perform advanced joins with filtering and transformations on the joined data -> Option C

4. Quick Check:

   $lookup with pipeline = advanced join [OK]

Hint: Remember: pipeline lets you filter joined data inside $lookup [OK]

Common Mistakes:

• Thinking $lookup with pipeline updates or deletes data
• Confusing $lookup with index creation
• Assuming $lookup merges collections permanently

2. Which of the following is the correct syntax to define variables for use inside the pipeline of a $lookup stage?

easy

A. "params: { var1: \"$field1\", var2: \"$field2\" }"

B. "vars: { var1: \"$field1\", var2: \"$field2\" }"

C. "variables: [ var1: \"$field1\", var2: \"$field2\" ]"

D. "let: { var1: \"$field1\", var2: \"$field2\" }"

Solution

1. Step 1: Recall $lookup variable syntax

   Variables for the pipeline are defined using the let keyword as an object.

2. Step 2: Match correct keyword and structure

   Only let with an object of key-value pairs is valid syntax.

3. Final Answer:

   "let: { var1: \"$field1\", var2: \"$field2\" }" -> Option D

4. Quick Check:

   Variables in $lookup pipeline = let [OK]

Hint: Use 'let' keyword with object to define variables in $lookup [OK]

Common Mistakes:

• Using 'vars' or 'variables' instead of 'let'
• Using array syntax instead of object for variables
• Omitting the $ sign before field names

3. Given collections orders and products, what will be the output of this aggregation on orders?

{
  $lookup: {
    from: "products",
    let: { prod_id: "$productId" },
    pipeline: [
      { $match: { $expr: { $eq: ["$_id", "$$prod_id"] } } },
      { $project: { name: 1, price: 1, _id: 0 } }
    ],
    as: "productDetails"
  }
}

medium

A. Each order document will have a 'productDetails' field with only product IDs

B. Each order document will have a new field 'productDetails' containing an array with matching product's name and price

C. The query will throw a syntax error due to incorrect variable reference

D. The 'productDetails' field will be a single object, not an array

Solution

1. Step 1: Understand $lookup with pipeline and let

   The let defines prod_id from orders.productId. The pipeline matches products._id to this variable.

2. Step 2: Analyze pipeline stages

   The pipeline filters products matching the order's productId and projects only name and price fields, excluding _id.

3. Final Answer:

   Each order document will have a new field 'productDetails' containing an array with matching product's name and price -> Option B

4. Quick Check:

   $lookup with pipeline returns array of matched docs [OK]

Hint: Remember $lookup with pipeline returns array in 'as' field [OK]

Common Mistakes:

• Expecting a single object instead of an array
• Using wrong variable reference syntax like '$prod_id' instead of '$$prod_id'
• Forgetting to project fields inside pipeline

4. Identify the error in this $lookup stage:

{
  $lookup: {
    from: "employees",
    let: { empId: "$employeeId" },
    pipeline: [
      { $match: { $expr: { $eq: ["$_id", "$$empId"] } } }
    ],
    as: "employeeInfo"
  }
}

medium

A. Variable reference inside $expr should be "$$empId" instead of "$empId"

B. The let keyword is not allowed inside $lookup

C. The from field must be an array, not a string

D. The as field cannot be named employeeInfo

Solution

1. Step 1: Check variable usage in $expr

   Variables defined in let must be referenced with double dollar signs $$ inside the pipeline.

2. Step 2: Identify incorrect variable reference

   The code uses "$empId" instead of "$$empId", causing a runtime error.

3. Final Answer:

   Variable reference inside $expr should be "$$empId" instead of "$empId" -> Option A

4. Quick Check:

   Use $$ to reference let variables inside pipeline [OK]

Hint: Use double $$ to reference let variables inside pipeline [OK]

Common Mistakes:

• Using single $ instead of double $$ for let variables
• Misplacing let outside $lookup
• Incorrect data type for 'from' field

5. You want to join orders with products but only include products priced above 100 in the joined array. Which $lookup pipeline correctly achieves this?

hard

A. { $lookup: { from: "products", let: { pid: "$productId" }, pipeline: [ { $match: { $expr: { $and: [ { $eq: ["$_id", "$$pid"] }, { $gt: ["$price", 100] } ] } } } ], as: "expensiveProduct" } }

B. { $lookup: { from: "products", localField: "productId", foreignField: "_id", as: "expensiveProduct", pipeline: [ { $match: { price: { $gt: 100 } } } ] } }

C. { $lookup: { from: "products", let: { pid: "$productId" }, pipeline: [ { $match: { _id: "$$pid", price: { $gt: 100 } } } ], as: "expensiveProduct" } }

D. { $lookup: { from: "products", let: { pid: "$productId" }, pipeline: [ { $match: { $expr: { $eq: ["$_id", "$$pid"] } } }, { $match: { price: { $gt: 100 } } } ], as: "expensiveProduct" } }

Solution

1. Step 1: Understand filtering with $expr and $and

   We must match documents where _id equals the variable and price is greater than 100 in a single $match using $expr and $and.

2. Step 2: Analyze each option's pipeline

   { $lookup: { from: "products", let: { pid: "$productId" }, pipeline: [ { $match: { $expr: { $and: [ { $eq: ["$_id", "$$pid"] }, { $gt: ["$price", 100] } ] } } } ], as: "expensiveProduct" } } correctly uses $expr with $and combining both conditions. { $lookup: { from: "products", localField: "productId", foreignField: "_id", as: "expensiveProduct", pipeline: [ { $match: { price: { $gt: 100 } } } ] } } wrongly uses pipeline with localField/foreignField which is invalid. { $lookup: { from: "products", let: { pid: "$productId" }, pipeline: [ { $match: { _id: "$$pid", price: { $gt: 100 } } } ], as: "expensiveProduct" } } uses invalid $match syntax inside pipeline. { $lookup: { from: "products", let: { pid: "$productId" }, pipeline: [ { $match: { $expr: { $eq: ["$_id", "$$pid"] } } }, { $match: { price: { $gt: 100 } } } ], as: "expensiveProduct" } } splits conditions into two $match stages, but second $match cannot use field without $expr inside pipeline.

3. Final Answer:

   Option A correctly filters joined products priced above 100 using $expr and $and -> Option A

4. Quick Check:

   Use $expr with $and for multiple conditions in $lookup pipeline [OK]

Hint: Combine conditions inside one $match using $expr and $and [OK]

Common Mistakes:

• Using localField/foreignField with pipeline together
• Splitting conditions into multiple $match without $expr
• Incorrect $match syntax inside pipeline