TF-IDF and BM25 scoring in Elasticsearch - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to set the similarity to BM25 in the Elasticsearch index settings.

Elasticsearch

{
  "settings": {
    "similarity": {
      "default": {
        "type": "[1]"
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Abm25

Btfidf

Cclassic

Dboolean

Attempts:

3 left

💡 Hint

Common Mistakes

Using "tfidf" which is not a valid similarity type in Elasticsearch.

Using "classic" which refers to TF-IDF but is deprecated.

Using "boolean" which is a different similarity model.

BM25 is the default and recommended similarity algorithm in Elasticsearch for scoring.

2fill in blank

medium

Complete the query to use the classic TF-IDF similarity for a specific field.

Elasticsearch

{
  "mappings": {
    "properties": {
      "content": {
        "type": "text",
        "similarity": "[1]"
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Abm25

Btfidf

Cboolean

Dclassic

Attempts:

3 left

💡 Hint

Common Mistakes

Using "tfidf" which is not a valid similarity type in Elasticsearch.

Using "bm25" which is the default but not TF-IDF.

Using "boolean" which is a different similarity model.

The "classic" similarity uses the TF-IDF scoring model in Elasticsearch.

3fill in blank

hard

Fix the error in the BM25 parameter setting to adjust the k1 parameter.

Elasticsearch

{
  "settings": {
    "similarity": {
      "my_bm25": {
        "type": "bm25",
        "k1": [1]
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

A1.2

Btrue

Ck1

D"1.2"

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the number in quotes making it a string.

Using the parameter name as the value.

Using boolean values instead of numbers.

The k1 parameter must be a numeric value, not a string or other type.

4fill in blank

hard

Fill both blanks to create a custom similarity with BM25 and set the b parameter.

Elasticsearch

{
  "settings": {
    "similarity": {
      "custom_bm25": {
        "type": "[1]",
        "b": [2]
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Abm25

Bclassic

C0.75

D1.5

Attempts:

3 left

💡 Hint

Common Mistakes

Using "classic" instead of "bm25" for the similarity type.

Setting b to a value greater than 1 or as a string.

Confusing b with k1 parameter.

BM25 similarity type is "bm25" and the b parameter controls length normalization, commonly set to 0.75.

5fill in blank

hard

Fill all three blanks to define a custom BM25 similarity with k1 and b parameters and apply it to a field.

Elasticsearch

{
  "settings": {
    "similarity": {
      "custom_bm25": {
        "type": "[1]",
        "k1": [2],
        "b": [3]
      }
    }
  },
  "mappings": {
    "properties": {
      "description": {
        "type": "text",
        "similarity": "custom_bm25"
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Abm25

B1.2

C0.75

Dclassic

Attempts:

3 left

💡 Hint

Common Mistakes

Using "classic" instead of "bm25" for the type.

Putting numeric parameters in quotes.

Omitting the similarity setting in the field mapping.

Custom BM25 similarity requires type "bm25" and numeric parameters k1 and b, commonly 1.2 and 0.75 respectively.

Practice

1. What is the main difference between TF-IDF and BM25 scoring in Elasticsearch?

easy

A. BM25 ignores inverse document frequency, TF-IDF uses it heavily.

B. TF-IDF is the default scoring algorithm in Elasticsearch, BM25 is optional.

C. BM25 considers term frequency saturation and document length normalization, TF-IDF does not.

D. TF-IDF scores are always higher than BM25 scores for the same query.

Solution

1. Step 1: Understand TF-IDF basics

   TF-IDF scores words by multiplying term frequency (TF) with inverse document frequency (IDF), but it does not adjust for document length or term frequency saturation.

2. Step 2: Understand BM25 improvements

   BM25 improves TF-IDF by adding term frequency saturation (diminishing returns for repeated terms) and normalizing by document length, making scores more balanced.

3. Final Answer:

   BM25 considers term frequency saturation and document length normalization, TF-IDF does not. -> Option C

4. Quick Check:

   BM25 adds saturation and length normalization [OK]

Hint: BM25 adjusts TF-IDF with saturation and length normalization [OK]

Common Mistakes:

• Thinking TF-IDF is default in Elasticsearch
• Believing BM25 ignores IDF
• Assuming TF-IDF always scores higher

2. Which Elasticsearch query parameter correctly switches the similarity scoring to TF-IDF instead of BM25?

easy

A. ""{
"similarity": "classic"
}"""

B. ""{
"similarity": "bm25"
}"""

C. ""{
"similarity": "tfidf"
}"""

D. ""{
"similarity": "default"
}"""

Solution

1. Step 1: Recall Elasticsearch similarity options

   Elasticsearch uses "bm25" by default. To switch to TF-IDF, you use the "classic" similarity setting.

2. Step 2: Match parameter to TF-IDF

   The "classic" similarity corresponds to TF-IDF scoring, so setting "similarity": "classic" enables TF-IDF.

3. Final Answer:

   { "similarity": "classic" } -> Option A

4. Quick Check:

   TF-IDF similarity is "classic" [OK]

Hint: Use similarity: classic to enable TF-IDF scoring [OK]

Common Mistakes:

• Using "tfidf" as similarity name (not valid)
• Assuming "default" switches to TF-IDF
• Confusing bm25 with TF-IDF

3. Given the following Elasticsearch query using BM25, what will happen to the score if a term appears multiple times in a document?

medium

A. The score increases but with diminishing returns due to term frequency saturation.

B. The score increases linearly with each additional term occurrence.

C. The score stays the same regardless of term frequency.

D. The score decreases as term frequency increases.

Solution

1. Step 1: Understand BM25 term frequency effect

   BM25 applies a saturation function to term frequency, so each additional occurrence adds less to the score than the previous one.

2. Step 2: Compare to linear increase

   Unlike TF-IDF which can increase linearly, BM25 limits the impact of repeated terms to avoid overvaluing them.

3. Final Answer:

   The score increases but with diminishing returns due to term frequency saturation. -> Option A

4. Quick Check:

   BM25 uses saturation, not linear increase [OK]

Hint: BM25 scores repeated terms with diminishing returns [OK]

Common Mistakes:

• Assuming linear score increase with term frequency
• Thinking score stays constant with repeats
• Believing score decreases with more terms

4. You configured Elasticsearch to use TF-IDF similarity but notice search results are not ranking as expected. Which of the following is a likely cause?

medium

A. TF-IDF requires a special query syntax different from standard queries.

B. TF-IDF does not use inverse document frequency, so scores are random.

C. BM25 must be disabled in the cluster settings to use TF-IDF.

D. You forgot to reindex the data after changing similarity settings.

Solution

1. Step 1: Understand similarity changes require reindexing

   Changing similarity settings affects how documents are scored, but Elasticsearch applies these only after reindexing the data.

2. Step 2: Identify common mistake

   If you don't reindex, old scores remain, so results won't reflect the new TF-IDF similarity.

3. Final Answer:

   You forgot to reindex the data after changing similarity settings. -> Option D

4. Quick Check:

   Reindexing needed after similarity change [OK]

Hint: Always reindex after changing similarity settings [OK]

Common Mistakes:

• Believing TF-IDF ignores IDF
• Thinking BM25 must be disabled cluster-wide
• Assuming query syntax changes for TF-IDF

5. You want to improve search relevance for a collection of very short documents using Elasticsearch. Which scoring approach and adjustment is best to handle short documents effectively?

hard

A. Use BM25 with a higher k1 parameter to ignore term frequency saturation.

B. Use BM25 with a lower b parameter to reduce length normalization effect.

C. Use TF-IDF similarity because it handles short documents better by default.

D. Use TF-IDF and disable inverse document frequency to boost short docs.

Solution

1. Step 1: Understand BM25 parameters for short docs

   BM25's b parameter controls length normalization. Lowering b reduces penalty on short documents, improving their scores.

2. Step 2: Compare to TF-IDF and other options

   TF-IDF lacks length normalization control. Increasing k1 ignores saturation, which can hurt relevance. Disabling IDF is incorrect.

3. Final Answer:

   Use BM25 with a lower b parameter to reduce length normalization effect. -> Option B

4. Quick Check:

   Lower b helps short docs in BM25 [OK]

Hint: Lower BM25 b parameter to favor short documents [OK]

Common Mistakes:

• Assuming TF-IDF is better for short docs by default
• Increasing k1 to ignore saturation hurts relevance
• Disabling IDF reduces search quality