Fuzzy matching in Elasticsearch - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Fuzzy query with max_expansions effect

What is the output of this Elasticsearch fuzzy query when searching for the term "roam" with max_expansions set to 2?

Elasticsearch

{
  "query": {
    "fuzzy": {
      "name": {
        "value": "roam",
        "fuzziness": 1,
        "max_expansions": 2
      }
    }
  }
}

A Matches documents with terms like "roam", "foam", but limits to 2 expanded terms

B Matches only exact term "roam" ignoring fuzziness

C Matches all terms within fuzziness 1 without limit on expansions

D Raises an error because max_expansions cannot be set to 2

💡 Hint

Think about how max_expansions limits the number of fuzzy variations Elasticsearch considers.

The max_expansions parameter limits how many fuzzy variations Elasticsearch will try. Setting it to 2 means it will consider only two possible fuzzy matches like "foam" and "roam". It does not disable fuzziness or cause errors.

🧠 Conceptual

intermediate

Understanding fuzziness parameter

Which statement correctly describes the fuzziness parameter in Elasticsearch fuzzy queries?

A It controls the maximum number of terms returned by the fuzzy query.

B It sets the minimum number of characters a term must have to be fuzzy matched.

C It defines the maximum Levenshtein edit distance allowed between the query term and matching terms.

D It disables fuzzy matching and forces exact matches only.

💡 Hint

Fuzziness relates to how different the matched words can be from the query word.

Fuzziness defines the maximum number of single-character edits (insertions, deletions, substitutions) allowed to consider a term a match.

🔧 Debug

advanced

Why does this fuzzy query return no results?

Given this fuzzy query searching for "aple" with fuzziness 1, why does it return no results?

Elasticsearch

{
  "query": {
    "fuzzy": {
      "name": {
        "value": "aple",
        "fuzziness": 1,
        "prefix_length": 3
      }
    }
  }
}

A Because the field "name" is not analyzed, so fuzzy matching fails

B Because prefix_length 3 requires first 3 characters to match exactly, but "aple" and "apple" differ in first 3 chars

C Because fuzzy queries do not support prefix_length parameter

D Because fuzziness 1 is too low to match "apple" from "aple"

💡 Hint

Check how prefix_length affects which characters must match exactly.

prefix_length 3 means the first 3 characters must be identical. "aple" and "apple" differ at the third character, so no match occurs despite fuzziness.

📝 Syntax

advanced

Identify the syntax error in this fuzzy query

Which option contains the correct syntax for a fuzzy query searching for "color" with fuzziness 2?

A { "query": { "fuzzy": { "color": { "value": "color", fuzziness: 2 } } } }

B { "query": { "fuzzy": { "color": { value: "color", "fuzziness": 2 } } } }

C { "query": { "fuzzy": { "color": { "value": "color", "fuzziness" = 2 } } } }

D { "query": { "fuzzy": { "color": { "value": "color", "fuzziness": 2 } } } }

💡 Hint

Remember JSON requires keys and string values to be in double quotes and colons to separate keys and values.

Option D uses correct JSON syntax with quoted keys and values and colons. Options A and D miss quotes on keys, and C uses '=' instead of ':', all invalid JSON.

🚀 Application

expert

Optimizing fuzzy search for typo tolerance in product names

You want to allow fuzzy matching on product names to tolerate up to 2 typos but avoid too many irrelevant matches. Which query configuration best balances fuzziness and performance?

A { "query": { "fuzzy": { "product_name": { "value": "sneaker", "fuzziness": 2, "max_expansions": 50, "prefix_length": 1 } } } }

B { "query": { "fuzzy": { "product_name": { "value": "sneaker", "fuzziness": 2, "max_expansions": 1000, "prefix_length": 0 } } } }

C { "query": { "fuzzy": { "product_name": { "value": "sneaker", "fuzziness": 1, "max_expansions": 10, "prefix_length": 3 } } } }

D { "query": { "fuzzy": { "product_name": { "value": "sneaker", "fuzziness": 3, "max_expansions": 5, "prefix_length": 2 } } } }

💡 Hint

Consider how fuzziness, max_expansions, and prefix_length affect match tolerance and query speed.

Option A allows up to 2 typos (fuzziness=2), limits expansions to 50 to avoid performance issues, and requires first character to match exactly (prefix_length=1) to reduce irrelevant matches. Other options either allow too many expansions, too low fuzziness, or too high fuzziness causing poor balance.

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