Exists query in Elasticsearch - Time & Space Complexity

Time Complexity: Exists query

O(n)

Understanding Time Complexity

When using an exists query in Elasticsearch, we want to know how the search time changes as the data grows.

We ask: How does checking if a field exists scale with more documents?

Scenario Under Consideration

Analyze the time complexity of the following Elasticsearch query.

{
  "query": {
    "exists": {
      "field": "user"
    }
  }
}
    

This query finds all documents where the "user" field exists.

Identify Repeating Operations

Look at what repeats when Elasticsearch runs this query.

• Primary operation: Checking each document to see if the "user" field is present.
• How many times: Once for every document in the index.

How Execution Grows With Input

As the number of documents grows, the work to check each document grows too.

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

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

Final Time Complexity

Time Complexity: O(n)

This means the time to run the exists query grows in a straight line as the number of documents increases.

Common Mistake

[X] Wrong: "The exists query runs instantly no matter how many documents there are."

[OK] Correct: Even though Elasticsearch is fast, it still needs to check each document's fields, so more documents mean more work.

Interview Connect

Understanding how queries scale helps you write efficient searches and explain your choices clearly in real projects.

Self-Check

"What if we added a filter to only check documents in a certain date range? How would the time complexity change?"

Practice

1. What does the exists query do in Elasticsearch?

easy

A. Finds documents where a specific field is present

B. Finds documents where a field has a specific value

C. Deletes documents missing a field

D. Updates documents with a missing field

Solution

1. Step 1: Understand the purpose of the exists query

   The exists query checks if a field exists in documents, filtering those that have the field.

2. Step 2: Compare options with the query's function

   Only Finds documents where a specific field is present correctly describes this behavior; others describe different operations.

3. Final Answer:

   Finds documents where a specific field is present -> Option A

4. Quick Check:

   Exists query = finds documents with field [OK]

Hint: Exists query checks if a field is present in documents [OK]

Common Mistakes:

• Confusing exists query with term query
• Thinking it deletes or updates documents
• Assuming it checks field values

2. Which of the following is the correct syntax for an exists query in Elasticsearch?

easy

A. {"query": {"exists": {"field_name": "user"}}}

B. {"query": {"exists": "user"}}

C. {"query": {"exists": {"value": "user"}}}

D. {"query": {"exists": {"field": "user"}}}

Solution

1. Step 1: Recall the correct JSON structure for exists query

   The exists query requires a "field" key inside its object specifying the field name.

2. Step 2: Match options to correct syntax

   {"query": {"exists": {"field": "user"}}} matches the correct syntax: {"exists": {"field": "user"}}. Others use wrong keys or structure.

3. Final Answer:

   {"query": {"exists": {"field": "user"}}} -> Option D

4. Quick Check:

   Exists query syntax uses "field" key [OK]

Hint: Exists query needs "field" key inside its object [OK]

Common Mistakes:

• Using "value" or "field_name" instead of "field"
• Omitting the object braces around field
• Passing field as a string directly

3. Given the following Elasticsearch query, what documents will it return?

{"query": {"exists": {"field": "email"}}}

medium

A. Documents where the email field exists

B. Documents where the email field is missing

C. Documents where the email field is empty

D. All documents regardless of email field

Solution

1. Step 1: Analyze the query structure

   The query uses an exists query on the field "email", which filters documents having that field.

2. Step 2: Understand what exists means for documents

   Documents returned must have the "email" field present, regardless of its value.

3. Final Answer:

   Documents where the email field exists -> Option A

4. Quick Check:

   Exists query returns docs with field present [OK]

Hint: Exists query returns docs with the field present only [OK]

Common Mistakes:

• Thinking it returns docs missing the field
• Assuming empty fields are excluded
• Believing it returns all documents

4. Identify the error in this Elasticsearch exists query:

{"query": {"exists": {"field_name": "status"}}}

medium

A. The field value should be an array, not a string

B. The query should use "match" instead of "exists"

C. The key should be "field", not "field_name"

D. The query is missing a "filter" wrapper

Solution

1. Step 1: Check the key used inside exists query

   The exists query requires the key "field" to specify the field name.

2. Step 2: Compare the given key with the correct one

   The query uses "field_name" which is incorrect and causes an error.

3. Final Answer:

   The key should be "field", not "field_name" -> Option C

4. Quick Check:

   Exists query key = "field" [OK]

Hint: Use "field" key inside exists query, not "field_name" [OK]

Common Mistakes:

• Using incorrect key names inside exists query
• Confusing exists with match query
• Adding unnecessary wrappers

5. You want to find all documents where the field phone exists but is not empty or null. Which Elasticsearch query best achieves this?

hard

A. {"query": {"bool": {"must": [{"exists": {"field": "phone"}}, {"term": {"phone": ""}}]}}}

B. {"query": {"bool": {"must": [{"exists": {"field": "phone"}}, {"script": {"script": "doc['phone'].value != ''"}}]}}}

C. {"query": {"exists": {"field": "phone"}}}

D. {"query": {"exists": {"field": "phone"}, "term": {"phone": ""}}}

Solution

1. Step 1: Understand the requirement

   We want documents where "phone" exists and is not empty or null.

2. Step 2: Evaluate each option

   {"query": {"exists": {"field": "phone"}}} only checks existence, not emptiness. {"query": {"bool": {"must": [{"exists": {"field": "phone"}}, {"term": {"phone": ""}}]}}} incorrectly requires phone to be empty. {"query": {"exists": {"field": "phone"}, "term": {"phone": ""}}} has invalid syntax combining exists and term at same level. {"query": {"bool": {"must": [{"exists": {"field": "phone"}}, {"script": {"script": "doc['phone'].value != ''"}}]}}} uses a bool must with exists and a script checking phone is not empty, correctly filtering as needed.

3. Final Answer:

   {"query": {"bool": {"must": [{"exists": {"field": "phone"}}, {"script": {"script": "doc['phone'].value != ''"}}]}}} -> Option B

4. Quick Check:

   Exists + script to exclude empty = {"query": {"bool": {"must": [{"exists": {"field": "phone"}}, {"script": {"script": "doc['phone'].value != ''"}}]}}} [OK]

Hint: Combine exists with script to exclude empty values [OK]

Common Mistakes:

• Using exists alone without checking empty values
• Incorrectly combining queries at same level
• Assuming term query with empty string works for exclusion