Why relevance scoring ranks results in Elasticsearch - Performance Analysis

Time Complexity: Why relevance scoring ranks results

O(n x t)

Understanding Time Complexity

When Elasticsearch ranks search results by relevance, it calculates scores for each document. Understanding how the time to compute these scores grows helps us see how search speed changes as data grows.

We want to know: how does scoring time increase when more documents or terms are involved?

Scenario Under Consideration

Analyze the time complexity of this Elasticsearch query snippet that ranks documents by relevance score.

GET /my_index/_search
{
  "query": {
    "match": {
      "content": "search terms here"
    }
  }
}
    

This query searches the "content" field for matching terms and calculates a relevance score for each matching document to rank results.

Identify Repeating Operations

Look at what repeats when Elasticsearch scores results:

• Primary operation: Calculating relevance score for each matching document.
• How many times: Once per matching document, for all terms in the query.

How Execution Grows With Input

As the number of matching documents grows, scoring each one takes more time. Also, more query terms mean more calculations per document.

Input Size (n = matching docs)	Approx. Operations
10	10 x t
100	100 x t
1000	1000 x t

Pattern observation: The work grows roughly in direct proportion to the number of matching documents and query terms.

Final Time Complexity

Time Complexity: O(n x t)

This means the time to rank results grows linearly with the number of matching documents (n) and the number of query terms (t).

Common Mistake

[X] Wrong: "Scoring happens only once regardless of how many documents match."

[OK] Correct: Each matching document must be scored separately to compare relevance, so scoring time grows with matches.

Interview Connect

Knowing how scoring time grows helps you explain search performance clearly. It shows you understand how Elasticsearch handles ranking behind the scenes, a useful skill for real projects.

Self-Check

"What if we added filters that reduce matching documents before scoring? How would that affect the time complexity?"

Practice

1. What does relevance scoring in Elasticsearch primarily determine?

easy

A. How well a document matches the search query

B. The size of the document

C. The date when the document was created

D. The number of fields in the document

Solution

1. Step 1: Understand relevance scoring purpose

   Relevance scoring measures how closely a document matches the search query terms.

2. Step 2: Compare options to scoring concept

   Only How well a document matches the search query relates to matching quality, others are unrelated to scoring.

3. Final Answer:

   How well a document matches the search query -> Option A

4. Quick Check:

   Relevance scoring = match quality [OK]

Hint: Relevance scoring ranks by match quality, not metadata [OK]

Common Mistakes:

• Confusing scoring with document size
• Thinking scoring depends on creation date
• Assuming number of fields affects score

2. Which Elasticsearch query part directly influences relevance scoring?

easy

A. sort

B. match

C. filter

D. aggs

Solution

1. Step 1: Identify query parts affecting scoring

   The match query scores documents based on how well they match the query text.

2. Step 2: Differentiate from other parts

   filter and aggs do not affect scoring; sort orders results but doesn't calculate score.

3. Final Answer:

   match -> Option B

4. Quick Check:

   Match query = scoring influence [OK]

Hint: Match queries affect scoring; filters do not [OK]

Common Mistakes:

• Thinking filters affect scoring
• Confusing sort with scoring
• Assuming aggregations influence score

3. Given this Elasticsearch query snippet, which document will rank higher?

{
  "query": {
    "match": {
      "title": "apple"
    }
  }
}

Documents: 1. {"title": "apple pie recipe"} 2. {"title": "banana apple smoothie"} 3. {"title": "fruit salad"}

medium

A. Document 3

B. Document 2

C. Document 1

D. All have the same score

Solution

1. Step 1: Understand match query scoring

   Documents containing the exact term "apple" in the title get higher scores. Document 1 has "apple" at the start and is more focused.

2. Step 2: Compare documents by term presence

   Document 1 has "apple" prominently; Document 2 has "apple" but mixed with "banana"; Document 3 lacks "apple".

3. Final Answer:

   Document 1 -> Option C

4. Quick Check:

   Exact term presence = higher score [OK]

Hint: Exact term in title ranks higher than partial or missing [OK]

Common Mistakes:

• Assuming all documents score equally
• Choosing document without the term
• Ignoring term position and frequency

4. You wrote this Elasticsearch query but results are not ranked by relevance:

{
  "query": {
    "bool": {
      "filter": {
        "match": { "content": "coffee" }
      }
    }
  }
}

What is the main issue?

medium

A. "filter" does not calculate relevance scores

B. The "match" query is misspelled

C. The query must use "must_not" instead of "filter"

D. The field "content" does not exist

Solution

1. Step 1: Understand bool query filter behavior

   The filter clause filters documents but does not affect relevance scoring.

2. Step 2: Identify why scoring is missing

   Using filter with match disables scoring; to rank by relevance, use must instead.

3. Final Answer:

   "filter" does not calculate relevance scores -> Option A

4. Quick Check:

   Filter disables scoring, use must for relevance [OK]

Hint: Use must, not filter, for scoring queries [OK]

Common Mistakes:

• Thinking filter affects scoring
• Assuming match is misspelled
• Ignoring bool query clause differences

5. You want to rank documents by relevance but also exclude those with "draft" status. Which query correctly ranks by relevance and filters out drafts?

{
  "query": {
    "bool": {
      "must": {
        "match": { "text": "Elasticsearch" }
      },
      "filter": {
        "term": { "status": "draft" }
      }
    }
  }
}

hard

A. Use "filter" for both match and filtering drafts

B. Use "filter" for match and "must" for filtering drafts

C. Use "should" for both match and filtering drafts

D. Use "must" for match and "must_not" for filtering drafts

Solution

1. Step 1: Understand must and filter roles

   must runs scoring queries; filter filters without scoring; must_not excludes documents.

2. Step 2: Apply exclusion for drafts

   To exclude drafts, use must_not with a term filter on status "draft"; keep must for scoring match query.

3. Final Answer:

   Use "must" for match and "must_not" for filtering drafts -> Option D

4. Quick Check:

   Must scores, must_not excludes [OK]

Hint: Use must for scoring, must_not to exclude unwanted docs [OK]

Common Mistakes:

• Using filter to exclude documents (doesn't exclude)
• Using should which affects scoring differently
• Filtering match query disables scoring