Why should you care?

Help centers and course catalogs need “search lessons about replica sets” without building Elasticsearch on day one.

See it live — copy this example

Open mongosh or MongoDB Compass, select database nosqlverse, then run the example. Change one field and run again.

db.articles.insertMany([
  { title: "Replica set elections", body: "How primaries are chosen" },
  { title: "Sharding chunk migration", body: "Balancing data across shards" }
])
db.articles.createIndex({ title: "text", body: "text" })
db.articles.find({ $text: { $search: "replica elections" } }, { score: { $meta: "textScore" } })
  .sort({ score: { $meta: "textScore" } })

Run Example »

Edit the code below and click Run to see the result in Toolliyo’s live editor.

What happened?

• One text index covers title and body.
• $text searches tokens.
• Projecting and sorting by textScore ranks better matches first.
• Only one text index per collection is allowed.

Practice next

1. Insert articles and create the text index.
2. Search for "sharding" and "elections".
3. Try phrase search with \"replica set\" in $search.
4. Add weights: { title: 10, body: 5 } on createIndex.
5. Exclude stop words by relying on default language.

Remember

Text indexes enable $text search. Sort by textScore for relevance. One text index per collection.

In-app help search

Users type “failover” and articles rank by relevance.

Outcome: Support deflection improves without a separate search cluster yet.