Completamento automatico e corrispondenza fuzzy
I partecipanti configureranno un analizzatore di completamento automatico su un campo e scriveranno query fuzzy per gestire gli errori di battitura nell'input di ricerca degli utenti.
Completamento automatico e corrispondenza fuzzy è una lezione MongoDB Academy gratuita su CoddyKit. Questa è la lezione 3 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento MongoDB Academy, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso MongoDB Academy include 4 lezioni in totale.
Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.
Why Autocomplete and Fuzzy Search Matter
Modern search experiences require two key features: autocomplete (suggesting completions as the user types) and fuzzy matching (finding results even when the user misspells a query). These features significantly improve user experience—autocomplete reduces search friction by guiding users to valid queries, while fuzzy matching ensures a typo does not result in 'no results found'. Atlas Search provides both through dedicated operators and analyzers.
Configuring an Autocomplete Analyzer
Autocomplete requires a special field configuration in the Atlas Search index. Use the autocomplete data type in the index mapping for the field you want to support type-ahead. This causes Atlas to index n-grams and edge n-grams of the field value—substrings that match partial inputs. The tokenization option can be 'edgeGram' (left-anchored substrings) or 'nGram' (all substrings), with optional minGrams and maxGrams sizes.
// Atlas Search index definition with autocomplete field
{
'mappings': {
'dynamic': false,
'fields': {
'name': [
{
'type': 'string', // for regular text search
'analyzer': 'lucene.standard'
},
{
'type': 'autocomplete', // for type-ahead queries
'tokenization': 'edgeGram', // 'mongod' -> 'm', 'mo', 'mon', 'mong', 'mongo', 'mongod'
'minGrams': 2,
'maxGrams': 10
}
]
}
}
}Running an Autocomplete Query
Use the autocomplete operator inside a $search stage to perform type-ahead queries. Specify the query (the partial input typed so far) and the path (the autocomplete-indexed field). As the user types each character, send a new query and return the top suggestions sorted by score. Limit results to 5-10 suggestions for a responsive UI.
// As user types 'mon', suggest matching product names
async function getAutocompleteSuggestions(partialQuery) {
const results = await db.collection('products').aggregate([
{
$search: {
autocomplete: {
query: partialQuery, // e.g., 'mon' -> suggests 'Monitor', 'MongoDB Atlas', etc.
path: 'name'
}
}
},
{ $limit: 8 },
{ $project: { name: 1, _id: 0 } }
]).toArray();
return results.map(r => r.name);
}EdgeGram vs nGram Tokenization
edgeGram creates substrings anchored at the start of each word: 'MongoDB' produces 'Mo', 'Mon', 'Mong', 'Mongo', 'MongoD', 'MongoDB'. This matches queries that start with the correct characters—a good default for name search. nGram creates all substrings of a word, enabling mid-word matching: 'ongo' would also match 'MongoDB'. nGram is more flexible but produces a much larger index and can return less precise suggestions.
// edgeGram: 'Python' generates:
// 'Py', 'Pyt', 'Pyth', 'Pytho', 'Python'
// -> matches queries starting with 'Py', 'Pyt', etc.
// nGram: 'Python' generates:
// 'Py', 'yt', 'th', 'ho', 'on', 'Pyt', 'yth', 'tho', ... etc.
// -> matches mid-word queries like 'ytho'
// For product name autocomplete, edgeGram is almost always the right choiceFuzzy Matching With the fuzzy Option
The text operator supports a fuzzy option that enables edit-distance based matching. It finds documents whose tokens are within a specified number of character edits (insertions, deletions, substitutions, transpositions) from the query tokens. This makes your search tolerant of typos. The maxEdits parameter controls tolerance (1 = one typo allowed, 2 = two typos).
// Fuzzy search: 'Monggodb' matches 'MongoDB' (1 extra 'g')
db.tutorials.aggregate([
{
$search: {
text: {
query: 'Monggodb aggregaton', // two typos
path: 'title',
fuzzy: {
maxEdits: 1, // allow 1 edit per token
prefixLength: 3 // first 3 chars must match exactly
}
}
}
},
{ $limit: 10 }
])Fuzzy Parameters: maxEdits and prefixLength
maxEdits can be 1 or 2 (Lucene does not support higher values). Higher values increase recall but reduce precision—with maxEdits: 2, many unrelated words may match. prefixLength specifies how many characters at the start of each query token must match exactly before fuzzy matching applies. A prefix length of 2-3 balances performance and accuracy, preventing the algorithm from fuzzy-matching against every token in the index.
// Conservative fuzzy: only 1 edit, first 3 chars must be exact
// Good for search boxes where users make occasional typos
fuzzy: { maxEdits: 1, prefixLength: 3 }
// Aggressive fuzzy: 2 edits, no prefix requirement
// Useful for voice-to-text or low-quality input
fuzzy: { maxEdits: 2, prefixLength: 0 }
// Balanced (recommended default):
fuzzy: { maxEdits: 1, prefixLength: 2, maxExpansions: 50 }Combining Autocomplete and Fuzzy
Autocomplete and fuzzy matching serve different use cases but can be combined in a compound query. The autocomplete operator handles prefix matching as the user types, while fuzzy matching in a text operator helps when users submit a complete but misspelled query. A common pattern is to try autocomplete first (during typing) and switch to fuzzy text search when the user submits their query.
// Hybrid: autocomplete for prefix + fuzzy for full query
async function search(query, isTyping) {
if (isTyping) {
// During typing: use autocomplete
return db.collection('products').aggregate([
{ $search: { autocomplete: { query, path: 'name' } } },
{ $limit: 6 },
{ $project: { name: 1 } }
]).toArray();
} else {
// On submit: use fuzzy text search
return db.collection('products').aggregate([
{ $search: { text: { query, path: ['name', 'description'], fuzzy: { maxEdits: 1 } } } },
{ $limit: 20 },
{ $project: { name: 1, price: 1, score: { $meta: 'searchScore' } } }
]).toArray();
}
}Token Order in Autocomplete
By default, the autocomplete operator matches the partial query against individual tokens (words) in the field. You can set tokenOrder: 'sequential' to require that the tokens appear in order—useful for multi-word inputs like 'node js' suggesting 'Node.js Developer Guide'. The default tokenOrder: 'any' returns results where any word starts with the prefix, regardless of order.
// Sequential token order: 'node js' must match 'Node.js' in order
db.courses.aggregate([
{
$search: {
autocomplete: {
query: 'node js',
path: 'title',
tokenOrder: 'sequential' // words must appear in this order
}
}
},
{ $limit: 5 }
])
// Any order: 'js node' would also match 'Node.js'
db.courses.aggregate([
{
$search: {
autocomplete: { query: 'js node', path: 'title', tokenOrder: 'any' }
}
}
])Debouncing Autocomplete Requests
Autocomplete queries fire on every keystroke, which can overwhelm your backend with rapid requests. Always implement debouncing on the client side—wait 200-300ms after the last keystroke before sending the query. Also cancel in-flight requests when a new one is issued to avoid out-of-order responses. In React, use a debounce hook or library; in a simple frontend, use clearTimeout and setTimeout.
// Simple debounce in JavaScript
let debounceTimer;
function onSearchInput(event) {
const query = event.target.value;
clearTimeout(debounceTimer);
debounceTimer = setTimeout(async () => {
if (query.length < 2) return; // minimum length check
const suggestions = await fetch('/api/autocomplete?q=' + encodeURIComponent(query));
renderSuggestions(await suggestions.json());
}, 250); // 250ms debounce
}Scoring and Relevance in Autocomplete
Atlas Search returns autocomplete results in order of their relevance score. Fields that have the query prefix at the beginning of the entire field value (rather than later in the string) receive higher scores. You can further influence scoring using the score option to boost, constant-score, or decay results based on other factors like popularity or recency. This ensures the most useful suggestions appear first.
// Boost products with higher view counts in autocomplete results
db.products.aggregate([
{
$search: {
autocomplete: {
query: 'wire',
path: 'name',
score: {
boost: {
path: 'viewCount', // boost by view count field
modifier: 'log1p' // log1p smoothing prevents extreme boosts
}
}
}
}
},
{ $limit: 8 },
{ $project: { name: 1, viewCount: 1 } }
])Minimum Query Length Best Practice
Avoid running autocomplete queries on very short inputs (1 character) as they return an overwhelming number of irrelevant suggestions and are expensive for the Lucene engine. Enforce a minimum query length of 2-3 characters before firing the autocomplete request. Similarly, for fuzzy matching, enable fuzzy only after the user has typed at least 3-4 characters to give Lucene enough context for meaningful edit-distance computation. These limits improve both performance and suggestion quality.
// Client-side minimum length enforcement
async function handleSearchInput(query) {
if (query.length < 2) {
clearSuggestions(); // don't search on 0 or 1 char
return;
}
// Autocomplete: good from 2 chars
if (query.length <= 4) {
return getAutocompleteSuggestions(query);
}
// Fuzzy search: enable after 4 chars for better precision
return getFuzzySearchResults(query);
}Quick Check
Test your understanding of MongoDB & NoSQL Databases concepts from this lesson.
Lesson Recap
In this lesson you learned: autocomplete requires an 'autocomplete' data type in the index mapping with tokenization (edgeGram or nGram) to index substrings, the autocomplete operator in $search enables prefix matching for type-ahead suggestions, and the text operator's fuzzy option uses edit-distance matching to handle typos with configurable maxEdits and prefixLength parameters. Next up we explore facets and compound queries for sophisticated search experiences.
Domande Frequenti
La lezione «Completamento automatico e corrispondenza fuzzy» è gratuita?
Sì — il testo completo di «Completamento automatico e corrispondenza fuzzy» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso MongoDB Academy, passa a CoddyKit PRO. Il corso MongoDB Academy include 4 lezioni in totale.
Cosa imparerò in «Completamento automatico e corrispondenza fuzzy»?
I partecipanti configureranno un analizzatore di completamento automatico su un campo e scriveranno query fuzzy per gestire gli errori di battitura nell'input di ricerca degli utenti. Eserciti MongoDB Academy con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.
Ho bisogno di esperienza per iniziare MongoDB Academy?
Non è richiesta alcuna esperienza precedente. MongoDB Academy su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 3 di 4.
Quanto tempo richiede la lezione «Completamento automatico e corrispondenza fuzzy»?
La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.
Posso scrivere ed eseguire codice in questa lezione MongoDB Academy?
Sì. Ogni lezione MongoDB Academy include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.
Tutte le lezioni di questo corso
- Creare un indice Atlas Search
- Scrivere query $search: testo, frasi e wildcard
- Completamento automatico e corrispondenza fuzzy
- Facet e query composte