Text search with text indexes in MongoDB - Time & Space Complexity

Time Complexity: Text search with text indexes

O(m)

Understanding Time Complexity

When using text search with text indexes in MongoDB, we want to know how the search time changes as the amount of data grows.

We ask: How does the search speed behave when the collection gets bigger?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Create a text index on the 'description' field
db.products.createIndex({ description: "text" })

// Search for documents containing the word 'coffee'
db.products.find({ $text: { $search: "coffee" } })

This code creates a text index on a field and then searches for documents matching a word using that index.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The database engine scans the text index entries related to the search term.
• How many times: It processes entries matching the search term, which depends on how many documents contain that word.

How Execution Grows With Input

As the number of documents grows, the index size grows too, but the search only looks at entries matching the search words.

Input Size (n)	Approx. Operations
10	Few index entries to check
100	More entries, but still limited to matching words
1000	More entries, search time grows with matches, not total documents

Pattern observation: The search time grows roughly with the number of matching documents, not the total collection size.

Final Time Complexity

Time Complexity: O(m)

This means the search time depends mostly on how many documents match the search term, not the total number of documents.

Common Mistake

[X] Wrong: "Text search scans every document in the collection every time."

[OK] Correct: The text index lets MongoDB quickly find matching documents without scanning all documents, so it only checks relevant entries.

Interview Connect

Understanding how text indexes speed up searches shows you know how databases handle big data efficiently, a useful skill for real projects and interviews.

Self-Check

"What if we searched for multiple words instead of one? How would the time complexity change?"

Practice

1. What is the main purpose of creating a text index in MongoDB?

easy

A. To store large text files efficiently

B. To speed up searching for words in text fields

C. To encrypt text fields for security

D. To sort documents by text fields alphabetically

Solution

1. Step 1: Understand what a text index does

   A text index allows MongoDB to quickly search for words inside text fields instead of scanning all documents.

2. Step 2: Compare options with the purpose

   Only To speed up searching for words in text fields matches the purpose of speeding up word searches. Other options describe unrelated features.

3. Final Answer:

   To speed up searching for words in text fields -> Option B

4. Quick Check:

   Text index purpose = speed up word search [OK]

Hint: Text indexes help find words fast in text fields [OK]

Common Mistakes:

• Confusing text index with sorting index
• Thinking text index encrypts data
• Assuming text index stores files

2. Which of the following is the correct syntax to create a text index on the field description in MongoDB?

easy

A. db.collection.createIndex({ description: 1 })

B. db.collection.createIndex({ description: 'string' })

C. db.collection.createTextIndex({ description: 1 })

D. db.collection.createIndex({ description: 'text' })

Solution

1. Step 1: Recall the syntax for text index creation

   The correct syntax uses createIndex with the field set to the string 'text'.

2. Step 2: Check each option

   db.collection.createIndex({ description: 'text' }) matches the correct syntax. db.collection.createIndex({ description: 'string' }) uses 'string' which is invalid. db.collection.createTextIndex({ description: 1 }) uses a non-existent method. db.collection.createIndex({ description: 1 }) creates a normal ascending index, not text.

3. Final Answer:

   db.collection.createIndex({ description: 'text' }) -> Option D

4. Quick Check:

   Text index syntax = createIndex({field: 'text'}) [OK]

Hint: Use createIndex with 'text' to make text indexes [OK]

Common Mistakes:

• Using 'string' instead of 'text'
• Using createTextIndex method (doesn't exist)
• Creating normal indexes instead of text indexes

3. Given a collection with a text index on the field content, what will the following query return?

db.articles.find({ $text: { $search: "mongodb tutorial" } })

medium

A. Documents containing either 'mongodb' or 'tutorial' in the content field

B. Documents containing both words 'mongodb' and 'tutorial' in the content field

C. Documents containing the exact phrase 'mongodb tutorial' only

D. Documents sorted alphabetically by content

Solution

1. Step 1: Understand $text and $search behavior

   The $search operator looks for documents containing any of the words listed, not necessarily all or exact phrases.

2. Step 2: Analyze the options

   Documents containing either 'mongodb' or 'tutorial' in the content field correctly states it returns documents containing either word. Documents containing both words 'mongodb' and 'tutorial' in the content field requires both words, which is not default. Documents containing the exact phrase 'mongodb tutorial' only requires exact phrase, which needs quotes. Documents sorted alphabetically by content is unrelated.

3. Final Answer:

   Documents containing either 'mongodb' or 'tutorial' in the content field -> Option A

4. Quick Check:

   $search finds any listed words by default [OK]

Hint: By default, $search matches any listed words [OK]

Common Mistakes:

• Assuming $search matches all words by default
• Thinking $search matches exact phrases without quotes
• Confusing search results with sorting

4. You run this query but get an error:

db.posts.find({ $text: { $search: "database" } })

What is the most likely cause?

medium

A. The query syntax requires parentheses

B. The $search operator is misspelled

C. No text index exists on the collection

D. The field name 'database' is invalid

Solution

1. Step 1: Understand requirements for $text queries

   MongoDB requires a text index on at least one field to use $text queries without error.

2. Step 2: Check the options for likely causes

   No text index exists on the collection correctly identifies missing text index as the cause. Other options describe syntax or spelling errors which are not present.

3. Final Answer:

   No text index exists on the collection -> Option C

4. Quick Check:

   $text query needs text index [OK]

Hint: Ensure text index exists before using $text queries [OK]

Common Mistakes:

• Ignoring the need for a text index
• Thinking $search syntax is wrong
• Assuming field names cause $text errors

5. You want to find documents that contain the exact phrase "fast search" in the summary field which has a text index. Which query will correctly do this?

hard

A. db.collection.find({ $text: { $search: '"fast search"' } })

B. db.collection.find({ $text: { $search: 'fast search' } })

C. db.collection.find({ summary: { $regex: 'fast search' } })

D. db.collection.find({ $text: { $search: '\"fast search\"' } })

Solution

1. Step 1: Recall how to search exact phrases with $text

   Exact phrase search requires double quotes around the phrase inside the $search string.

2. Step 2: Evaluate each option

   db.collection.find({ $text: { $search: '"fast search"' } }) correctly uses single quotes outside and double quotes inside to search exact phrase. db.collection.find({ $text: { $search: 'fast search' } }) searches words separately. db.collection.find({ summary: { $regex: 'fast search' } }) uses regex, not text search. db.collection.find({ $text: { $search: '\"fast search\"' } }) escapes quotes incorrectly.

3. Final Answer:

   db.collection.find({ $text: { $search: '"fast search"' } }) -> Option A

4. Quick Check:

   Exact phrase search = double quotes inside $search string [OK]

Hint: Use double quotes inside $search string for exact phrase [OK]

Common Mistakes:

• Not using quotes for exact phrase
• Using regex instead of text search
• Incorrectly escaping quotes