Phrase suggestions (did you mean) in Elasticsearch - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to add a phrase suggestion named "my-suggestion" to the search query.

Elasticsearch

{
  "suggest": {
    "my-suggestion": {
      "phrase": {
        "field": [1]
      }
    }
  }
}

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

A"content"

B"title"

C"message"

D"author"

Attempts:

3 left

💡 Hint

Common Mistakes

Using a field name that does not exist in the index.

Forgetting to put the field name in quotes.

The phrase suggestion requires the field name where the text is stored. "message" is the correct field here.

2fill in blank

medium

Complete the code to set the size of phrase suggestions to 3.

Elasticsearch

{
  "suggest": {
    "my-suggestion": {
      "phrase": {
        "field": "message",
        "size": [1]
      }
    }
  }
}

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

A3

B1

C5

D10

Attempts:

3 left

💡 Hint

Common Mistakes

Setting size to 0 or a negative number.

Using a string instead of a number.

The "size" parameter controls how many suggestions are returned. Setting it to 3 returns three suggestions.

3fill in blank

hard

Fix the error in the phrase suggestion by completing the code with the correct "text" parameter.

Elasticsearch

{
  "suggest": {
    "my-suggestion": {
      "text": [1],
      "phrase": {
        "field": "message"
      }
    }
  }
}

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

Ahelo wrld

B"helo wrld"

C"hello world"

Dhello world

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting quotes around the text string.

Using correct spelling instead of the misspelled text.

The "text" parameter must be a string enclosed in quotes. "helo wrld" is the misspelled text to suggest corrections for.

4fill in blank

hard

Fill both blanks to add a "direct_generator" with "suggest_mode" set to "always" inside the phrase suggestion.

Elasticsearch

{
  "suggest": {
    "my-suggestion": {
      "text": "helo wrld",
      "phrase": {
        "field": "message",
        "direct_generator": [
          {
            "suggest_mode": [1]
          }
        ]
      }
    }
  }
}

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

A"always"

B"popular"

C"missing"

D"never"

Attempts:

3 left

💡 Hint

Common Mistakes

Using suggest_mode values not supported by Elasticsearch.

Omitting quotes around the suggest_mode value.

The "suggest_mode" set to "always" means suggestions are generated for all tokens, even if they are correct.

5fill in blank

hard

Fill all three blanks to add a phrase suggestion with "text", "field", and "size" parameters correctly set.

Elasticsearch

{
  "suggest": {
    "my-suggestion": {
      "text": [1],
      "phrase": {
        "field": [2],
        "size": [3]
      }
    }
  }
}

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

A"spel cheker"

B"message"

C2

D"title"

Attempts:

3 left

💡 Hint

Common Mistakes

Putting numbers in quotes.

Omitting quotes around string values.

Using incorrect field names.

The "text" is the misspelled phrase, "field" is the text field to check, and "size" is how many suggestions to return.

Practice

1. What is the main purpose of phrase suggestions (did you mean) in Elasticsearch?

easy

A. To help fix typos and suggest correct phrases in search queries

B. To sort search results by relevance

C. To filter documents based on date ranges

D. To aggregate numeric data for analytics

Solution

1. Step 1: Understand phrase suggestions purpose

   Phrase suggestions are designed to detect and correct typos or mistakes in user search queries.

2. Step 2: Compare with other features

   Sorting, filtering, and aggregations serve different purposes unrelated to typo correction.

3. Final Answer:

   To help fix typos and suggest correct phrases in search queries -> Option A

4. Quick Check:

   Phrase suggestions = typo correction [OK]

Hint: Phrase suggestions fix typos in queries [OK]

Common Mistakes:

• Confusing phrase suggestions with sorting or filtering
• Thinking phrase suggestions aggregate data
• Assuming phrase suggestions change document content

2. Which of the following is the correct way to specify a phrase suggestion in an Elasticsearch query?

easy

A. "suggest": {"my-suggestion": {"completion": {"field": "content"}}}

B. "suggest": {"my-suggestion": {"term": {"field": "content"}}}

C. "suggest": {"my-suggestion": {"text": "exampl", "phrase": {"field": "content"}}}

D. "suggest": {"my-suggestion": {"match": {"field": "content"}}}

Solution

1. Step 1: Identify phrase suggestion syntax

   Phrase suggestions use the "phrase" type inside the suggest block with a specified field.

2. Step 2: Check other options

   Options A, B, and D use other suggestion types like completion, term, or match, which are not phrase suggestions.

3. Final Answer:

   "suggest": {"my-suggestion": {"text": "exampl", "phrase": {"field": "content"}}} -> Option C

4. Quick Check:

   Phrase suggestion uses "phrase" type [OK]

Hint: Phrase suggestions use "phrase" type in suggest [OK]

Common Mistakes:

• Using term or completion instead of phrase
• Omitting the "field" inside phrase
• Misplacing the "text" parameter

3. Given this Elasticsearch phrase suggestion snippet, what will be the size of suggestions returned?

{
  "suggest": {
    "text": "quik brown",
    "phrase": {
      "field": "body",
      "size": 3
    }
  }
}

medium

A. 1 suggestion

B. Unlimited suggestions

C. 5 suggestions

D. 3 suggestions

Solution

1. Step 1: Identify the size parameter

   The "size" parameter inside the phrase suggestion controls how many suggestions are returned.

2. Step 2: Check the value of size

   Here, "size" is set to 3, so Elasticsearch will return up to 3 suggestions.

3. Final Answer:

   3 suggestions -> Option D

4. Quick Check:

   Size = 3 means 3 suggestions [OK]

Hint: Check "size" to know number of suggestions [OK]

Common Mistakes:

• Assuming default size without checking parameter
• Confusing size with gram_size
• Thinking size limits characters, not suggestions

4. Identify the error in this phrase suggestion query:

{
  "suggest": {
    "my-suggest": {
      "text": "helo world",
      "phrase": {
        "field": "content",
        "gram_size": "two"
      }
    }
  }
}

medium

A. "gram_size" should be an integer, not a string

B. "text" parameter is missing

C. "field" should be an array, not a string

D. Phrase suggestions don't support 'gram_size' parameter

Solution

1. Step 1: Check the "gram_size" parameter type

   "gram_size" expects an integer value, but here it is given as a string "two".

2. Step 2: Verify other parameters

   "text" and "field" are correctly specified; phrase suggestions do support "gram_size".

3. Final Answer:

   "gram_size" should be an integer, not a string -> Option A

4. Quick Check:

   gram_size = integer, not string [OK]

Hint: Use numbers, not words, for gram_size [OK]

Common Mistakes:

• Passing gram_size as a string
• Removing the text parameter
• Changing field to an array unnecessarily

5. You want to suggest corrections for a user query with multiple words and control the phrase suggestion to consider 2-gram phrases. Which of the following is the correct way to configure the phrase suggestion in Elasticsearch?

hard

A. { "suggest": { "text": "spel cheker", "phrase": { "field": "text", "gram_size": 2, "size": 2 } } }

B. { "suggest": { "my-suggest": { "text": "spel cheker", "phrase": { "field": "text", "gram_size": 2, "size": 2 } } } }

C. { "suggest": { "my-suggest": { "text": "spel cheker", "term": { "field": "text", "gram_size": 2 } } } }

D. { "suggest": { "my-suggest": { "text": "spel cheker", "phrase": { "field": "text", "gram_size": "2", "size": 2 } } } }

Solution

1. Step 1: Check the suggest block structure

   The suggest block must have a named suggestion (e.g., "my-suggest") containing "text" and "phrase" parameters.

2. Step 2: Verify phrase suggestion parameters

   "gram_size" should be an integer (2), and "size" controls number of suggestions. { "suggest": { "my-suggest": { "text": "spel cheker", "phrase": { "field": "text", "gram_size": 2, "size": 2 } } } } correctly uses these.

3. Step 3: Eliminate incorrect options

   { "suggest": { "text": "spel cheker", "phrase": { "field": "text", "gram_size": 2, "size": 2 } } } misses the named suggestion key. { "suggest": { "my-suggest": { "text": "spel cheker", "term": { "field": "text", "gram_size": 2 } } } } uses "term" instead of "phrase". { "suggest": { "my-suggest": { "text": "spel cheker", "phrase": { "field": "text", "gram_size": "2", "size": 2 } } } } passes "gram_size" as a string, which is invalid.

4. Final Answer:

   { "suggest": { "my-suggest": { "text": "spel cheker", "phrase": { "field": "text", "gram_size": 2, "size": 2 } } } } -> Option B

5. Quick Check:

   Named suggest + phrase + integer gram_size = correct [OK]

Hint: Use named suggest with phrase and integer gram_size [OK]

Common Mistakes:

• Omitting the named suggestion key
• Using term instead of phrase
• Passing gram_size as a string