Text search with text indexes in MongoDB - Step-by-Step Execution

Concept Flow - Text search with text indexes

Create text index on fields

↓

Insert documents into collection

↓

Run text search query

↓

MongoDB uses text index to find matches

↓

Return matching documents

First, create a text index on the fields you want to search. Then insert documents. When you run a text search query, MongoDB uses the text index to quickly find matching documents and returns them.

Execution Sample

MongoDB

db.articles.createIndex({title: "text", content: "text"})
db.articles.insertMany([
  {title: "Coffee benefits", content: "Coffee is great for energy."},
  {title: "Tea facts", content: "Tea has antioxidants."}
])
db.articles.find({$text: {$search: "coffee"}})

Create a text index on title and content fields, insert two documents, then search for documents containing the word 'coffee'.

Execution Table

Step	Action	Input/Query	Index Used	Result
1	Create text index	{title: "text", content: "text"}	Text index on title and content	Index created
2	Insert documents	[{title: "Coffee benefits", content: "Coffee is great for energy."}, {title: "Tea facts", content: "Tea has antioxidants."}]	Index updated with new docs	2 documents inserted
3	Run text search	{$text: {$search: "coffee"}}	Text index used to find matches	1 document matched: {title: "Coffee benefits", content: "Coffee is great for energy."}
4	Return results	Matched documents	N/A	Returned 1 document
5	End	No more steps	N/A	Query complete

💡 Query ends after returning all matching documents found by the text index.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
textIndex	None	Created on title and content	Updated with 2 documents	Used to find matches for 'coffee'	Used and query completed
documents	Empty collection	Empty collection	2 documents inserted	1 document matched	Query complete

Key Moments - 3 Insights

Why do we need to create a text index before running a text search?

MongoDB uses the text index to quickly find matching documents. Without the index, the search would be slow or not work as expected. See execution_table step 1 and 3.

Does the text search match partial words or exact words?

Text search matches whole words and their variations, but not partial substrings. For example, searching 'coffee' matches 'coffee' but not 'coffeemaker'. See execution_table step 3.

What happens if we search for a word not in any document?

The text index is used but no documents match, so the query returns an empty result set. This is shown by no matched documents in step 3.

Visual Quiz - 3 Questions

Look at the execution_table, at which step is the text index created?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Check the 'Action' column for when the index is created.

According to variable_tracker, how many documents are in the collection after step 2?

A 0

B 2

C 1

D 3

💡 Hint

Look at the 'documents' row after Step 2.

If we searched for 'tea' instead of 'coffee', what would change in the execution_table at step 3?

A Both documents would match.

B No documents would match.

C The matched document would be the one with title 'Tea facts'.

D The index would be recreated.

💡 Hint

Consider which document contains the word 'tea' in the inserted data.

Concept Snapshot

Text search in MongoDB requires creating a text index on fields.
Insert documents into the collection.
Use {$text: {$search: "word"}} to find matching documents.
MongoDB uses the text index to quickly return results.
Search matches whole words and their variations.
No index means slower or no text search.

Full Transcript

This visual execution shows how MongoDB text search works with text indexes. First, you create a text index on the fields you want to search, like title and content. Then you insert documents into the collection. When you run a text search query using {$text: {$search: "word"}}, MongoDB uses the text index to quickly find matching documents. The execution table traces each step: creating the index, inserting documents, running the search, and returning results. The variable tracker shows how the index and documents change over time. Key moments clarify why the index is needed, how matching works, and what happens if no documents match. The quiz tests understanding of index creation, document count, and search results. The snapshot summarizes the process in a few lines for quick reference.

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