Graph lookup for recursive data in MongoDB - Time & Space Complexity

Time Complexity: Graph lookup for recursive data

O(n)

Understanding Time Complexity

When working with recursive data in MongoDB, we often use graph lookup to find connected items.

We want to understand how the time needed grows as the data size and connections increase.

Scenario Under Consideration

Analyze the time complexity of the following MongoDB graph lookup query.

db.employees.aggregate([
  {
    $graphLookup: {
      from: "employees",
      startWith: "$_id",
      connectFromField: "managerId",
      connectToField: "_id",
      as: "managementChain"
    }
  }
])
    

This query finds all managers above an employee by recursively following the managerId field.

Identify Repeating Operations

Look for repeated steps in the query execution.

• Primary operation: Recursively searching connected documents by following managerId links.
• How many times: Once per level of management chain until no more managers are found.

How Execution Grows With Input

The query explores each connected document in the chain, so more levels mean more work.

Input Size (n)	Approx. Operations
10	About 10 lookups if chain is long
100	Up to 100 lookups if chain is long
1000	Up to 1000 lookups if chain is long

Pattern observation: The work grows roughly linearly with the length of the recursive chain.

Final Time Complexity

Time Complexity: O(n)

This means the time grows in direct proportion to the number of connected documents found in the recursion.

Common Mistake

[X] Wrong: "Graph lookup always runs in constant time because it uses indexes."

[OK] Correct: Even with indexes, the query must visit each connected document, so time grows with the chain length.

Interview Connect

Understanding how recursive queries scale helps you explain data retrieval in hierarchical structures clearly and confidently.

Self-Check

"What if the graph lookup had a maxDepth limit? How would that affect the time complexity?"

Practice

1. What is the primary purpose of the $graphLookup stage in MongoDB aggregation?

easy

A. To create indexes on fields

B. To perform a simple filter on documents

C. To update multiple documents at once

D. To recursively search connected documents within the same collection

Solution

1. Step 1: Understand the role of $graphLookup

   $graphLookup is designed to recursively find related documents by following references within the same collection, useful for hierarchical data.

2. Step 2: Compare with other options

   Options B, C, and D describe other MongoDB operations unrelated to recursive lookup.

3. Final Answer:

   To recursively search connected documents within the same collection -> Option D

4. Quick Check:

   $graphLookup = recursive search [OK]

Hint: Remember $graphLookup is for recursive connected data search [OK]

Common Mistakes:

• Confusing $graphLookup with $match filtering
• Thinking $graphLookup updates documents
• Assuming $graphLookup creates indexes

2. Which of the following is the correct syntax to start a $graphLookup stage in a MongoDB aggregation pipeline?

easy

A. {"$graphLookup": {"from": "employees", "startWith": "$managerId", "connectFromField": "_id", "connectToField": "managerId", "as": "reportingHierarchy"}}

B. {"$graphLookup": {"from": "employees", "startWith": "$managerId", "connectFromField": "managerId", "connectToField": "_id", "as": "reportingHierarchy"}}

C. {"$graphLookup": {"from": "employees", "startWith": "managerId", "connectFromField": "_id", "connectToField": "managerId", "as": "reportingHierarchy"}}

D. {"$graphLookup": {"from": "employees", "startWith": "$id", "connectFromField": "managerId", "connectToField": "_id", "as": "reportingHierarchy"}}

Solution

1. Step 1: Identify correct field references

   In $graphLookup, startWith uses the field to start recursion, usually a reference like "$managerId". The connectToField is the field in the foreign documents to match against the start value, here "_id". The connectFromField is the field in the foreign document used for the next recursion, here "managerId".

2. Step 2: Match syntax with options

   {"$graphLookup": {"from": "employees", "startWith": "$managerId", "connectFromField": "managerId", "connectToField": "_id", "as": "reportingHierarchy"}} correctly uses startWith: "$managerId", connectFromField: "managerId", and connectToField: "_id". Others swap these or use incorrect field names.

3. Final Answer:

   {"$graphLookup": {"from": "employees", "startWith": "$managerId", "connectFromField": "managerId", "connectToField": "_id", "as": "reportingHierarchy"}} -> Option B

4. Quick Check:

   Correct field mapping = {"$graphLookup": {"from": "employees", "startWith": "$managerId", "connectFromField": "managerId", "connectToField": "_id", "as": "reportingHierarchy"}} [OK]

Hint: Match startWith with $field, connectToField with foreign _id [OK]

Common Mistakes:

• Swapping connectFromField and connectToField
• Missing $ in startWith field
• Using wrong field names for connections

3. Given the following collection categories with documents:

{"_id": 1, "name": "Electronics", "parent": null}

{"_id": 2, "name": "Computers", "parent": 1}

{"_id": 3, "name": "Laptops", "parent": 2}

What will be the result of this aggregation?

[ { "$graphLookup": { "from": "categories", "startWith": "$parent", "connectFromField": "parent", "connectToField": "_id", "as": "ancestors" } } ]

for the document with _id: 3?

medium

A. An array 'ancestors' containing documents with _id 2 and 1

B. An empty array 'ancestors'

C. An array 'ancestors' containing only document with _id 1

D. A syntax error due to incorrect $graphLookup usage

Solution

1. Step 1: Understand the recursive lookup

   Starting from the document with _id 3, startWith uses its parent field which is 2. Then it finds documents where _id matches 2, then recursively finds parents of 2, which is 1.

2. Step 2: Trace the ancestors found

   The recursion finds documents with _id 2 and then _id 1, so the 'ancestors' array contains both documents.

3. Final Answer:

   An array 'ancestors' containing documents with _id 2 and 1 -> Option A

4. Quick Check:

   Recursive parents = [2, 1] [OK]

Hint: Trace startWith field value and follow connectToField recursively [OK]

Common Mistakes:

• Assuming only direct parent is returned
• Confusing connectFromField and connectToField
• Expecting syntax error incorrectly

4. Consider this aggregation pipeline snippet:

{ "$graphLookup": { "from": "employees", "startWith": "$managerId", "connectFromField": "managerId", "connectToField": "_id", "as": "team" } }

Why might this pipeline fail or return empty results when run on an employee document with no managerId field?

medium

A. Because as field name is invalid

B. Because connectFromField and connectToField are swapped

C. Because startWith is null or missing, recursion cannot start

D. Because from collection does not exist

Solution

1. Step 1: Check the startWith field value

   If the document has no managerId field, startWith evaluates to null or undefined, so the recursion has no starting point.

2. Step 2: Understand impact on results

   Without a valid start value, $graphLookup returns an empty array for 'team' because it cannot find connected documents.

3. Final Answer:

   Because startWith is null or missing, recursion cannot start -> Option C

4. Quick Check:

   Missing startWith value = empty results [OK]

Hint: Ensure startWith field exists and is not null [OK]

Common Mistakes:

• Thinking connectFromField/connectToField swap causes empty results
• Assuming 'as' field name causes failure
• Ignoring missing 'from' collection errors

5. You have a collection employees where each document has _id and managerId. You want to find all employees under a manager recursively, including the manager. Which $graphLookup configuration correctly achieves this?

hard

A. {"$graphLookup": {"from": "employees", "startWith": "$_id", "connectFromField": "_id", "connectToField": "managerId", "as": "team"}}

B. {"$graphLookup": {"from": "employees", "startWith": "$managerId", "connectFromField": "managerId", "connectToField": "_id", "as": "team"}}

C. {"$graphLookup": {"from": "employees", "startWith": "$_id", "connectFromField": "managerId", "connectToField": "_id", "as": "team"}}

D. {"$graphLookup": {"from": "employees", "startWith": "$managerId", "connectFromField": "_id", "connectToField": "managerId", "as": "team"}}

Solution

1. Step 1: Define the recursion direction

   To find all employees under a manager, start with the manager's _id. Then find employees whose managerId matches this _id, recursively.

2. Step 2: Match fields in $graphLookup

   startWith should be $_id (the manager's id). connectToField is managerId (field in employees to match), and connectFromField is _id (field to match against for next level).

3. Step 3: Verify options

   {"$graphLookup": {"from": "employees", "startWith": "$_id", "connectFromField": "_id", "connectToField": "managerId", "as": "team"}} matches this logic exactly. {"$graphLookup": {"from": "employees", "startWith": "$_id", "connectFromField": "managerId", "connectToField": "_id", "as": "team"}} swaps connectFromField and connectToField incorrectly. The options starting with $managerId are wrong for this use case.

4. Final Answer:

   {"$graphLookup": {"from": "employees", "startWith": "$_id", "connectFromField": "_id", "connectToField": "managerId", "as": "team"}} -> Option A

5. Quick Check:

   Start with manager _id, connectFromField = _id, connectToField = managerId = {"$graphLookup": {"from": "employees", "startWith": "$_id", "connectFromField": "_id", "connectToField": "managerId", "as": "team"}} [OK]

Hint: Start with manager _id, connectFromField = _id, connectToField = managerId [OK]

Common Mistakes:

• Swapping connectFromField and connectToField
• Starting with $managerId instead of $_id
• Confusing direction of recursion