Match phrase query in Elasticsearch - Time & Space Complexity

Time Complexity: Match phrase query

O(n)

Understanding Time Complexity

When we use a match phrase query in Elasticsearch, it looks for exact sequences of words in documents.

We want to understand how the time to find these phrases grows as we search more documents or longer texts.

Scenario Under Consideration

Analyze the time complexity of the following Elasticsearch match phrase query.

GET /my_index/_search
{
  "query": {
    "match_phrase": {
      "content": "quick brown fox"
    }
  }
}
    

This query searches for documents where the words "quick brown fox" appear together in that exact order in the "content" field.

Identify Repeating Operations

Look at what repeats when Elasticsearch runs this query.

• Primary operation: Scanning each document's "content" field to find the phrase.
• How many times: Once per document in the search scope.

How Execution Grows With Input

As the number of documents grows, Elasticsearch checks more texts for the phrase.

Input Size (n documents)	Approx. Operations
10	10 phrase checks
100	100 phrase checks
1000	1000 phrase checks

Pattern observation: The work grows directly with the number of documents checked.

Final Time Complexity

Time Complexity: O(n)

This means the time to find the phrase grows linearly with the number of documents searched.

Common Mistake

[X] Wrong: "The phrase query checks only a few documents, so it is always very fast."

[OK] Correct: Even if the phrase is rare, Elasticsearch must scan many documents to find matches, so time grows with document count.

Interview Connect

Understanding how phrase queries scale helps you explain search performance clearly and shows you know how search engines work under the hood.

Self-Check

"What if we changed the match phrase query to a simple match query? How would the time complexity change?"

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