Match phrase query in Elasticsearch - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a match phrase query in Elasticsearch?

A match phrase query searches for a sequence of words in the exact order within a text field. It helps find documents where the phrase appears exactly as typed.

beginner

How does a match phrase query differ from a match query?

A match query looks for documents containing all the words anywhere in the text, regardless of order. A match phrase query requires the words to appear together in the exact order.

intermediate

What is the purpose of the slop parameter in a match phrase query?

The slop parameter allows some flexibility by letting words in the phrase be a few positions apart. It helps find phrases with small gaps or word swaps.

beginner

Write a simple match phrase query to find the phrase "quick brown fox" in the field "content".

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

intermediate

What happens if you set slop to 2 in a match phrase query?

Setting slop to 2 allows up to two word positions to be skipped or swapped in the phrase. This means the phrase can match even if words are slightly out of order or separated by up to two words.

What does a match phrase query in Elasticsearch do?

A Searches for any of the words in any order

B Searches for numeric values only

C Searches only for single words

D Searches for an exact sequence of words in order

A match phrase query looks for the exact sequence of words in the specified order.

Which parameter controls how much word order flexibility a match phrase query allows?

A slop

B boost

C fuzziness

D analyzer

The slop parameter controls how many positions words can be apart or swapped.

If you want to find documents containing the phrase "data science" exactly, which query should you use?

A term query

B match phrase query

C match query

D range query

A match phrase query finds the exact phrase in the text.

What happens if you omit the slop parameter in a match phrase query?

A The query requires the phrase words to be adjacent and in order

B The query searches only the first word

C The query ignores word order

D The query allows unlimited word gaps

Without slop, the phrase must appear exactly with words adjacent and in order.

Which Elasticsearch query type is best for searching a phrase with possible small word swaps?

A match query

B term query

C match phrase query with slop

D prefix query

Match phrase query with slop allows small word swaps or gaps.

Explain what a match phrase query is and how it works in Elasticsearch.

Think about searching for exact sentences or phrases in a book.

Describe the role of the slop parameter in a match phrase query and give an example of when you might use it.

Imagine searching for a phrase but allowing small word gaps or swaps.

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