MongoDB Academy · 课时

文本索引的限制及何时使用 Atlas Search

您将识别原生文本索引的限制——每个集合只能有一个索引以及语言支持范围——并判断何时 Atlas Search 是更好的选择。

文本索引的限制及何时使用 Atlas Search 是 CoddyKit 上的免费 MongoDB Academy 课时。这是第 4 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 MongoDB Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 MongoDB Academy 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Text Index Limitations Overview

MongoDB's built-in text index is a great starting point for full-text search, but it has several important limitations that become significant as your search requirements grow. Understanding these constraints helps you decide early whether to invest in the native text index or migrate to a dedicated search engine like Atlas Search.

One Text Index Per Collection

The most impactful limitation is that each collection can have only one text index. This means you cannot have separate text indexes for different search scenarios on the same collection—everything must be combined into a single index definition. If your search requirements change and you need to add or remove fields from the index, you must drop and rebuild the entire text index, which can be time-consuming on large collections.

// Can't have two text indexes on the same collection
db.articles.createIndex({ title: 'text' });  // OK
// db.articles.createIndex({ body: 'text' });  // ERROR!

// Must combine everything into one:
db.articles.dropIndex('title_text');  // rebuild required
db.articles.createIndex({ title: 'text', body: 'text' });

No Autocomplete Support

Native text indexes have no autocomplete capability. They match whole words (after stemming) but cannot suggest completions for partial input. For example, searching for 'mongo' will NOT match documents containing 'mongodb' because 'mongo' and 'mongodb' stem to different tokens. Implementing autocomplete with native text indexes requires complex workarounds like storing n-grams, which is inefficient.

// Native text index: partial word does NOT match
db.articles.find({ $text: { $search: 'mongo' } });
// Will NOT return docs with 'mongodb' because
// 'mongo' stems to 'mongo', 'mongodb' stems to 'mongodb'
// These are different index tokens

// Atlas Search: autocomplete field supports partial matching
// { $search: { autocomplete: { query: 'mongo', path: 'title' } } }

No Fuzzy Matching

Native text indexes have no fuzzy (approximate) matching. A typo like 'mongodab' will not match 'mongodb'—the token must be close enough to stem to the same root. For user-facing search boxes where typos are common, this results in frustrating zero-result searches. Atlas Search provides a fuzzy option with configurable edit distance to handle typos gracefully.

// Native $text: typo returns NO results
db.articles.find({ $text: { $search: 'mongodab' } }); // 0 results

// Atlas Search fuzzy option handles typos
// db.articles.aggregate([{
//   $search: {
//     text: {
//       query: 'mongodab',
//       path: 'title',
//       fuzzy: { maxEdits: 2 }  // tolerates up to 2 character edits
//     }
//   }
// }]);

Limited Language Support

Native text indexes support around 15 languages for stemming and stop words. While this covers most Western European languages, it has no support for Chinese, Japanese, Korean, Arabic, and many other languages that require word-boundary detection before tokenisation. Atlas Search uses Lucene analyzers that support a much broader set of languages and script-specific tokenisation rules.

// Supported natively: english, french, german, spanish, portuguese,
// italian, dutch, danish, norwegian, swedish, finnish,
// romanian, turkish, russian (with caveats)

// NOT supported natively:
// Chinese (no word boundaries), Japanese, Korean, Arabic
// Must use Atlas Search or an external search engine for these
db.articles.createIndex({ body: 'text' }, { default_language: 'english' });

No Synonym Support

Native text indexes cannot expand search terms to include synonyms. If a user searches for 'automobile', documents containing only 'car' will not match. Atlas Search supports synonym mappings that you configure in the index definition, enabling rich synonym expansion without application-level query rewriting.

// Native text: no synonym expansion
// 'car' search does NOT match 'automobile' documents
db.articles.find({ $text: { $search: 'car' } });

// Workaround: client-side synonym expansion (brittle)
const synonyms = { car: ['automobile', 'vehicle', 'auto'] };
const expandedSearch = [search, ...synonyms[search]].join(' ');
db.articles.find({ $text: { $search: expandedSearch } });

// Atlas Search: configure synonyms in the index definition

Performance at Scale

Native text indexes store all tokens in a single WiredTiger B-tree within the same storage engine as your operational data. For large corpora (tens of millions of documents with long text fields), this can cause write amplification and cache pressure that degrades overall database performance. Dedicated search engines like Lucene (which powers Atlas Search) are architecturally optimised for large token stores using inverted indexes with compression.

// Monitor text index size vs other indexes
const stats = db.articles.stats();
console.log('Index sizes:', stats.indexSizes);
// If text index is 10x larger than next biggest index,
// consider Atlas Search to offload the storage overhead

What Is Atlas Search?

Atlas Search is a fully managed, Apache Lucene-based search engine built into MongoDB Atlas. It runs as a separate service within your Atlas cluster and replicates data from your collections automatically. Atlas Search uses the aggregation $search stage rather than $text, and it provides autocomplete, fuzzy matching, facets, synonyms, custom scoring, and deep language support—all with the same MongoDB connection string.

// Atlas Search uses $search aggregation stage
db.articles.aggregate([
  { $search: {
    text: {
      query: 'mongodb tutorial',
      path: ['title', 'body'],
      fuzzy: { maxEdits: 1 }
    }
  }},
  { $limit: 10 },
  { $project: { title: 1, score: { $meta: 'searchScore' } } }
]);

Decision Matrix: Text Index vs Atlas Search

Use the native text index when: your collection has fewer than 1 million documents; your users search in one Western European language; you need basic keyword search with no typos or autocomplete; you want zero additional infrastructure cost. Use Atlas Search when: you need autocomplete or fuzzy search; your user base searches in multiple or non-Latin-script languages; you need faceted navigation; or your text search is central to the product and must scale.

// Native text: simple, zero extra cost, one language
// Good for: admin search, internal tools, small product
db.products.createIndex({ name: 'text', description: 'text' });

// Atlas Search: richer, requires Atlas M10+ cluster
// Good for: customer-facing search, multilingual, autocomplete
// Create via Atlas UI or API, then use $search in aggregation

Migrating From Text Index to Atlas Search

Migrating from native text to Atlas Search does not require changing your data model—Atlas Search indexes the same collection. The migration steps are: 1) create an Atlas Search index on the collection via the Atlas UI or API; 2) rewrite your find({ $text: ... }) queries to use the $search aggregation stage; 3) test and validate results; 4) drop the old text index to free up storage. Your documents don't move; only the index and query syntax change.

// BEFORE (native text)
db.articles.find(
  { $text: { $search: 'mongodb' } },
  { score: { $meta: 'textScore' } }
).sort({ score: { $meta: 'textScore' } });

// AFTER (Atlas Search - same result set, richer options)
db.articles.aggregate([
  { $search: { text: { query: 'mongodb', path: ['title', 'body'] } } },
  { $addFields: { score: { $meta: 'searchScore' } } },
  { $sort: { score: -1 } }
]);

When Neither Is Enough

For very demanding search requirements—custom ML-based ranking, vector similarity search (semantic search), multi-tenancy at scale, or full observability into query plans—even Atlas Search may not suffice. In those cases, dedicated search platforms like Elasticsearch, Solr, or Typesense are used alongside MongoDB, with a synchronisation layer (change streams or ETL) keeping the search index in sync with the MongoDB source of truth.

// Architecture pattern: MongoDB + external search engine
// 1. Write data to MongoDB (source of truth)
// 2. Change stream replicates new/updated docs to Elasticsearch
// 3. Search queries go to Elasticsearch
// 4. Read queries for known IDs go directly to MongoDB

// MongoDB change stream listener (Node.js)
const changeStream = db.articles.watch();
for await (const change of changeStream) {
  await elasticsearchClient.index({ id: change.documentKey._id, ...change.fullDocument });
}

Quick Check

Test your understanding of text index limitations and Atlas Search.

Lesson Recap

In this lesson you learned: native text indexes have key limitations including one-per-collection, no autocomplete, no fuzzy matching, and limited language support, Atlas Search (Lucene-based) solves these with autocomplete, fuzzy, synonyms, and broad language coverage, and the right choice depends on scale and feature requirements. Next up we explore array operators and queries.

常见问题解答

「文本索引的限制及何时使用 Atlas Search」课时是免费的吗？

是的 — 「文本索引的限制及何时使用 Atlas Search」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 MongoDB Academy 课程的其余内容，请升级到 CoddyKit PRO。 MongoDB Academy 课程共包含 4 节课。

「文本索引的限制及何时使用 Atlas Search」这节课中我会学到什么？

您将识别原生文本索引的限制——每个集合只能有一个索引以及语言支持范围——并判断何时 Atlas Search 是更好的选择。你通过在浏览器中直接运行的动手代码来练习 MongoDB Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 MongoDB Academy 需要有经验吗？

无需任何先前经验。CoddyKit 上的 MongoDB Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 4 节课，共 4 节。

「文本索引的限制及何时使用 Atlas Search」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 MongoDB Academy 课中编写并运行代码吗？

能。每节 MongoDB Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 MongoDB Academy