Fuzzy matching in Elasticsearch - Step-by-Step Execution

Concept Flow - Fuzzy matching

Input Query

↓

Apply Fuzziness

↓

Search Index for Similar Terms

↓

Calculate Similarity Score

↓

Return Matches Above Threshold

↓

Display Results

The search query is processed with fuzziness to find terms similar to the input, then results with high similarity scores are returned.

Execution Sample

Elasticsearch

{
  "query": {
    "fuzzy": {
      "name": {
        "value": "roam",
        "fuzziness": "AUTO"
      }
    }
  }
}

This query searches for documents where the 'name' field matches terms similar to 'roam' using automatic fuzziness.

Execution Table

Step	Action	Input	Fuzziness Applied	Similarity Score	Result
1	Receive query	name: 'roam'	AUTO	-	Start search
2	Generate variants	roam	AUTO	-	roam, room, foam, roam...
3	Search index	variants	AUTO	Calculated per term	Find matching documents
4	Calculate similarity	each variant vs index terms	AUTO	0.8, 0.9, 0.7, ...	Score each match
5	Filter results	scores	AUTO	>= threshold	Keep matches with high score
6	Return results	filtered matches	AUTO	-	Documents with similar terms to 'roam'
7	End	-	-	-	Search complete

💡 Search ends after returning documents with similarity scores above threshold.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
query	{name: 'roam'}	{name: 'roam'}	{variants generated}	{scores calculated}	{filtered matches}
variants	none	[roam, room, foam]	[roam, room, foam]	[roam, room, foam]	[roam, room]
similarity_scores	none	none	none	[0.9, 0.8, 0.7]	[0.9, 0.8]
results	none	none	none	none	[docs matching 'roam' and 'room']

Key Moments - 3 Insights

Why does the query find 'room' when searching for 'roam'?

Because fuzziness allows small differences, the execution_table row 2 shows variants like 'room' generated from 'roam'.

What does the similarity score represent?

It measures how close a variant term is to the original query term, as shown in execution_table row 4.

Why are some variants filtered out?

Only variants with similarity scores above a threshold are kept, as explained in execution_table row 5.

Visual Quiz - 3 Questions

Look at the execution_table, what is the similarity score for the variant 'room'?

A 0.8

B 0.9

C 0.7

D 1.0

💡 Hint

Check execution_table row 4 under Similarity Score column.

At which step are variants like 'foam' generated from 'roam'?

A Step 2

B Step 4

C Step 1

D Step 6

💡 Hint

Look at execution_table row 2 describing variant generation.

If fuzziness was set to 0, how would the variants change?

A More variants generated

B Variants with large differences generated

C No variants generated, exact match only

D Variants ignored, all results returned

💡 Hint

Fuzziness controls allowed differences; 0 means exact match only, see concept_flow step 'Apply Fuzziness'.

Concept Snapshot

Fuzzy matching in Elasticsearch:
- Uses 'fuzzy' query with 'value' and 'fuzziness' params
- Finds terms similar to input (typos, close spellings)
- Generates variants automatically with 'AUTO' fuzziness
- Scores similarity and filters results
- Useful for typo-tolerant search

Full Transcript

Fuzzy matching in Elasticsearch works by taking the input query term and generating similar variants based on allowed differences called fuzziness. The query then searches the index for these variants, calculates similarity scores for each match, and returns documents with scores above a threshold. For example, searching for 'roam' with fuzziness 'AUTO' generates variants like 'room' and 'foam'. Each variant is scored for similarity, and only close matches are returned. This helps find results even if the search term has typos or small differences. The process starts with receiving the query, generating variants, searching the index, scoring matches, filtering results, and finally returning the matched documents.

Practice

1. What does the fuzziness parameter control in an Elasticsearch fuzzy query?

easy

A. The maximum length of the search term

B. The number of allowed letter changes to match similar words

C. The minimum number of exact matches required

D. The number of search results returned

Solution

1. Step 1: Understand the role of fuzziness

   The fuzziness parameter sets how many letters can be changed, added, or removed to still count as a match.

2. Step 2: Compare options with definition

   Only The number of allowed letter changes to match similar words correctly describes this as controlling allowed letter changes for similar words.

3. Final Answer:

   The number of allowed letter changes to match similar words -> Option B

4. Quick Check:

   Fuzziness = allowed letter changes [OK]

Hint: Fuzziness = allowed letter changes in matching [OK]

Common Mistakes:

• Confusing fuzziness with result count
• Thinking fuzziness limits search term length
• Mixing fuzziness with prefix_length

2. Which of the following is the correct syntax to add fuzziness in an Elasticsearch query DSL?

easy

A. "match": { "field": { "query": "text", "fuzzify": 2 } }

B. "match": { "field": { "query": "text", "fuzzy": true } }

C. "match": { "field": { "query": "text", "fuzziness": "AUTO" } }

D. "match": { "field": { "query": "text", "fuzzy_level": "high" } }

Solution

1. Step 1: Recall correct fuzziness syntax

   Elasticsearch uses the fuzziness parameter inside the match query with values like "AUTO" or a number.

2. Step 2: Check each option

   Only "match": { "field": { "query": "text", "fuzziness": "AUTO" } } uses the correct key "fuzziness" and proper structure.

3. Final Answer:

   "match": { "field": { "query": "text", "fuzziness": "AUTO" } } -> Option C

4. Quick Check:

   Correct fuzziness syntax = "match": { "field": { "query": "text", "fuzziness": "AUTO" } } [OK]

Hint: Use "fuzziness" key with "AUTO" or number [OK]

Common Mistakes:

• Using incorrect keys like fuzzy or fuzzify
• Setting fuzziness outside the match query
• Using boolean true instead of fuzziness value

3. Given this Elasticsearch fuzzy query snippet:

{ "match": { "name": { "query": "roam", "fuzziness": 0, "prefix_length": 1 } } }

Which of these terms will match the query?

medium

A. "roam"

B. "foam"

C. "roams"

D. "roan"

Solution

1. Step 1: Understand fuzziness and prefix_length

   Fuzziness 0 allows no letter differences (exact match). Prefix_length 1 means first letter must match exactly.

2. Step 2: Check each option against rules

   "roam" matches exactly. "foam" differs in first letter (prefix_length=1), so no. "roams" has extra letter, no exact match. "roan" differs by one letter after prefix ('m' vs 'n'), but fuzziness=0 allows no changes, so no.

3. Final Answer:

   "roam" -> Option A

4. Quick Check:

   Exact match with prefix_length = "roam" [OK]

Hint: Prefix_length fixes first letters; fuzziness=0 requires exact match [OK]

Common Mistakes:

• Ignoring prefix_length effect on first letter
• Assuming all similar words match regardless of prefix
• Confusing fuzziness with allowed extra letters

4. You wrote this fuzzy query:

{ "match": { "title": { "query": "elastic", "fuzziness": "2", "prefix_length": 3 } } }

But it returns no results even though documents with "plastics" and "elustics" exist. What is the likely problem?

medium

A. prefix_length is too high, blocking matches with differences in first 3 letters

B. fuzziness value must be a boolean, not a number

C. query string "elastic" is misspelled

D. match query does not support fuzziness parameter

Solution

1. Step 1: Analyze prefix_length effect

   Prefix_length 3 means first 3 letters must match exactly. If documents differ in those letters, they won't match.

2. Step 2: Check fuzziness and query validity

   Fuzziness accepts numbers; "2" is valid. Query "elastic" is correct. Match query supports fuzziness.

3. Final Answer:

   prefix_length is too high, blocking matches with differences in first 3 letters -> Option A

4. Quick Check:

   High prefix_length blocks fuzzy matches = prefix_length is too high, blocking matches with differences in first 3 letters [OK]

Hint: High prefix_length blocks fuzzy matches early [OK]

Common Mistakes:

• Thinking fuzziness must be boolean
• Ignoring prefix_length effect
• Assuming match query disallows fuzziness

5. You want to find documents with names similar to "johnson" allowing up to 2 letter changes but want to speed up search by requiring the first 2 letters to match exactly. Which query is best?

hard

A. { "match": { "name": { "query": "johnson", "fuzziness": "AUTO", "prefix_length": 3 } } }

B. { "match": { "name": { "query": "johnson", "fuzziness": 1, "prefix_length": 0 } } }

C. { "match": { "name": { "query": "johnson", "fuzziness": 3, "prefix_length": 1 } } }

D. { "match": { "name": { "query": "johnson", "fuzziness": 2, "prefix_length": 2 } } }

Solution

1. Step 1: Match requirements to parameters

   Allow up to 2 letter changes means fuzziness = 2. Speed up by requiring first 2 letters exact means prefix_length = 2.

2. Step 2: Evaluate each option

   { "match": { "name": { "query": "johnson", "fuzziness": 2, "prefix_length": 2 } } } matches both requirements exactly. { "match": { "name": { "query": "johnson", "fuzziness": 1, "prefix_length": 0 } } } allows only 1 change and no prefix. { "match": { "name": { "query": "johnson", "fuzziness": "AUTO", "prefix_length": 3 } } } uses AUTO fuzziness and prefix_length 3, which is more restrictive. { "match": { "name": { "query": "johnson", "fuzziness": 3, "prefix_length": 1 } } } allows 3 changes but only 1 prefix letter.

3. Final Answer:

   { "match": { "name": { "query": "johnson", "fuzziness": 2, "prefix_length": 2 } } } -> Option D

4. Quick Check:

   Fuzziness 2 + prefix_length 2 = { "match": { "name": { "query": "johnson", "fuzziness": 2, "prefix_length": 2 } } } [OK]

Hint: Match fuzziness and prefix_length to requirements exactly [OK]

Common Mistakes:

• Using wrong fuzziness number
• Setting prefix_length too high or too low
• Confusing AUTO with exact fuzziness number