Match phrase query in Elasticsearch - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a match_phrase query searching for "quick brown" in the "message" field.

Elasticsearch

{
  "query": {
    "match_phrase": {
      "message": [1]
    }
  }
}

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

A"quick brown"

B"quick"

C"brown"

D"quick brown fox"

Attempts:

3 left

💡 Hint

Common Mistakes

Using only one word instead of the full phrase.

Not putting the phrase inside quotes.

The match_phrase query requires the exact phrase as a string value. Here, "quick brown" is the phrase to match.

2fill in blank

medium

Complete the code to add a slop of 2 to the match_phrase query for "quick fox" in the "message" field.

Elasticsearch

{
  "query": {
    "match_phrase": {
      "message": {
        "query": "quick fox",
        "[1]": 2
      }
    }
  }
}

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

Aboost

Bfuzziness

Cslop

Danalyzer

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'boost' instead of 'slop'.

Confusing 'fuzziness' with 'slop'.

The slop parameter allows matching phrases with words in between, controlling how far apart the words can be.

3fill in blank

hard

Fix the error in the match_phrase query by completing the missing key for the phrase "lazy dog" in the "content" field.

Elasticsearch

{
  "query": {
    "match_phrase": {
      "content": {
        [1]: "lazy dog"
      }
    }
  }
}

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

A"phrase"

B"match"

C"text"

D"query"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'phrase' or 'match' instead of 'query'.

Omitting the key and just putting the string.

The key query is required to specify the phrase string inside the match_phrase query object.

4fill in blank

hard

Fill both blanks to create a match_phrase query on the "title" field with phrase "open source" and slop 1.

Elasticsearch

{
  "query": {
    "match_phrase": {
      "title": {
        "[1]": "open source",
        "[2]": 1
      }
    }
  }
}

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

Aquery

Bslop

Cboost

Danalyzer

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping 'boost' or 'analyzer' for 'slop'.

Using 'phrase' instead of 'query'.

The query key holds the phrase string, and slop controls the allowed distance between words.

5fill in blank

hard

Fill all three blanks to create a match_phrase query on the "description" field with phrase "fast car", slop 3, and boost 2.0.

Elasticsearch

{
  "query": {
    "match_phrase": {
      "description": {
        "[1]": "fast car",
        "[2]": 3,
        "[3]": 2.0
      }
    }
  }
}

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

Aquery

Bslop

Cboost

Danalyzer

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up 'boost' and 'slop' keys.

Using 'analyzer' instead of 'boost'.

The keys query, slop, and boost specify the phrase, allowed word distance, and importance weight respectively.

Practice

1. What does a match_phrase query in Elasticsearch do?

easy

A. Searches only for single words, ignoring phrases.

B. Searches for any of the words in the query, regardless of order.

C. Searches for an exact sequence of words in the given order.

D. Searches for documents with numeric values only.

Solution

1. Step 1: Understand the purpose of match_phrase

   The match_phrase query looks for the exact sequence of words in the order they appear in the query.

2. Step 2: Compare with other query types

   Unlike match query, which finds any word in any order, match_phrase requires the phrase to appear exactly.

3. Final Answer:

   Searches for an exact sequence of words in the given order. -> Option C

4. Quick Check:

   match_phrase = exact word order search [OK]

Hint: Remember: match_phrase means exact words in exact order [OK]

Common Mistakes:

• Confusing match_phrase with match query
• Thinking it ignores word order
• Assuming it works only for single words

2. Which of the following is the correct syntax for a match_phrase query in Elasticsearch?

easy

A. { "match": { "field": "search text" } }

B. { "match_phrase": { "field": "search text" } }

C. { "term": { "field": "search text" } }

D. { "range": { "field": { "gte": 10 } } }

Solution

1. Step 1: Identify the correct query type

   The match_phrase query uses the key "match_phrase" with the field and the phrase to search.

2. Step 2: Check the syntax format

   The correct syntax is a JSON object with "match_phrase" as the key and the field name mapping to the phrase string.

3. Final Answer:

   { "match_phrase": { "field": "search text" } } -> Option B

4. Quick Check:

   Correct JSON syntax for match_phrase = { "match_phrase": { "field": "search text" } } [OK]

Hint: Look for "match_phrase" key with field and phrase inside braces [OK]

Common Mistakes:

• Using "match" instead of "match_phrase"
• Confusing with "term" or "range" queries
• Incorrect JSON structure or missing braces

3. Given this Elasticsearch query:

{ "query": { "match_phrase": { "description": "quick brown fox" } } }

Which documents will match?

medium

A. Documents containing the words "fox brown quick" in any order.

B. Documents containing any of the words "quick", "brown", or "fox" in any order.

C. Documents containing the phrase "quick fox brown" exactly.

D. Documents containing the phrase "quick brown fox" exactly in that order.

Solution

1. Step 1: Analyze the match_phrase query

   The query searches for the exact phrase "quick brown fox" in the field "description".

2. Step 2: Understand phrase matching behavior

   Only documents with the words in the exact order "quick brown fox" will match, not any other order or partial words.

3. Final Answer:

   Documents containing the phrase "quick brown fox" exactly in that order. -> Option D

4. Quick Check:

   Exact phrase match = Documents containing the phrase "quick brown fox" exactly in that order. [OK]

Hint: match_phrase requires exact word order in the phrase [OK]

Common Mistakes:

• Assuming word order does not matter
• Thinking partial word matches count
• Confusing with match query behavior

4. You wrote this query but it returns no results:

{ "query": { "match_phrase": { "title": "fast runner" } } }

Your documents contain the phrase "runner fast". What is the issue?

medium

A. The phrase order is incorrect; match_phrase requires exact order.

B. The field name "title" is invalid.

C. match_phrase does not support multi-word phrases.

D. The query syntax is wrong; it should use "match" instead.

Solution

1. Step 1: Check phrase order in query vs documents

   The query searches for "fast runner" but documents have "runner fast" which is reversed.

2. Step 2: Understand match_phrase behavior

   match_phrase requires the exact word order, so reversed order causes no matches.

3. Final Answer:

   The phrase order is incorrect; match_phrase requires exact order. -> Option A

4. Quick Check:

   Exact order matters in match_phrase = The phrase order is incorrect; match_phrase requires exact order. [OK]

Hint: Check word order carefully when match_phrase returns no hits [OK]

Common Mistakes:

• Ignoring word order importance
• Assuming match_phrase works like match
• Changing field name unnecessarily

5. You want to find documents containing the phrase "data science" but also allow a gap of one word between "data" and "science". Which match_phrase query option should you use?

hard

A. { "match_phrase": { "field": "data science", "slop": 1 } }

B. { "match_phrase": { "field": "data science", "boost": 1 } }

C. { "match": { "field": "data science", "slop": 1 } }

D. { "term": { "field": "data science" } }

Solution

1. Step 1: Understand phrase slop in match_phrase

   The "slop" parameter allows words to appear with gaps or reordered within a limit.

2. Step 2: Identify correct syntax for slop

   Using "slop": 1 inside the match_phrase query allows one word gap between "data" and "science".

3. Final Answer:

   { "match_phrase": { "field": "data science", "slop": 1 } } -> Option A

4. Quick Check:

   Use slop to allow gaps in match_phrase = { "match_phrase": { "field": "data science", "slop": 1 } } [OK]

Hint: Add "slop" to match_phrase to allow word gaps [OK]

Common Mistakes:

• Using slop with match instead of match_phrase
• Confusing boost with slop
• Using term query for phrase matching