Bool query (must, should, must_not, filter) in Elasticsearch - Time & Space Complexity
When using a bool query in Elasticsearch, it's important to know how the search time changes as we add more conditions.
We want to understand how the number of conditions affects the work Elasticsearch does.
Analyze the time complexity of the following bool query.
{
"query": {
"bool": {
"must": [ { "match": { "title": "search" } } ],
"should": [ { "term": { "status": "published" } } ],
"must_not": [ { "range": { "date": { "lt": "2023-01-01" } } } ],
"filter": [ { "term": { "category": "books" } } ]
}
}
}
This query combines several conditions to find documents matching all must, some should, excluding must_not, and applying filters.
Look at how many times Elasticsearch checks each condition.
- Primary operation: Checking each document against all conditions in must, should, must_not, and filter.
- How many times: Once per document for each condition group.
As the number of documents grows, Elasticsearch checks each document against the bool query conditions.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | About 10 document checks |
| 100 | About 100 document checks |
| 1000 | About 1000 document checks |
Pattern observation: The work grows roughly in direct proportion to the number of documents.
Time Complexity: O(n)
This means the time to run the query grows linearly with the number of documents to check.
[X] Wrong: "Adding more conditions in must, should, or filter does not affect query time much."
[OK] Correct: Each added condition means more checks per document, so the total work increases with more conditions.
Understanding how bool queries scale helps you explain how search engines handle complex filters efficiently.
What if we added nested bool queries inside must? How would the time complexity change?
Practice
Solution
Step 1: Understand bool query clauses
The bool query has four main clauses:must(required),should(optional),must_not(exclude), andfilter(limit without scoring).Step 2: Identify exclusion clause
Themust_notclause excludes documents that match its conditions from the results.Final Answer:
must_not-> Option BQuick Check:
Exclude = must_not [OK]
- Confusing must_not with must
- Using should to exclude documents
- Thinking filter excludes documents
must clause inside a bool query in Elasticsearch?Solution
Step 1: Recall bool must clause syntax
Themustclause expects an array of query objects inside the bool query.Step 2: Check each option's syntax
"bool": { "must": [ { "match": { "field": "value" } } ] } correctly uses an array with onematchquery object. The other options use incorrect types or missing brackets.Final Answer:
"bool": { "must": [ { "match": { "field": "value" } } ] } -> Option AQuick Check:
Must clause = array of queries [OK]
- Using object instead of array for must
- Missing brackets around match query
- Using parentheses instead of brackets
{
"bool": {
"must": [{ "term": { "status": "active" }}],
"should": [{ "term": { "role": "admin" }}],
"must_not": [{ "term": { "banned": true }}]
}
}Solution
Step 1: Analyze must clause effect
Themustclause requires documents to havestatus: active.Step 2: Analyze should and must_not clauses
Theshouldclause means documents withrole: adminare preferred but not required. Themust_notclause excludes documents wherebannedis true.Final Answer:
Documents with status 'active', optionally role 'admin', excluding banned ones -> Option DQuick Check:
Must + optional should + exclude must_not = Documents with status 'active', optionally role 'admin', excluding banned ones [OK]
- Thinking should is required
- Ignoring must_not exclusion
- Confusing must and should roles
{
"bool": {
"must": { "match": { "title": "Elasticsearch" } },
"filter": { "term": { "status": "published" } },
"must_not": [ { "term": { "archived": true } } ]
}
}Solution
Step 1: Check must clause format
Themustclause expects an array of query objects, but here it is given as a single object.Step 2: Validate other clauses
Thefilterandmust_notclauses are correctly formatted as an object and an array respectively.Final Answer:
"must" should be an array, not an object -> Option AQuick Check:
Must clause = array required [OK]
- Using object instead of array for must
- Thinking filter and must_not conflict
- Using array for must_not incorrectly
category is 'books' and the price is less than 20, but exclude those that are out of stock. Which bool query correctly implements this?Solution
Step 1: Identify required conditions
Documents must havecategory: booksandprice < 20. Both are required, so they go inmustas an array.Step 2: Exclude out of stock documents
Documents withstock: outmust be excluded, so usemust_notwith an array of term queries.Step 3: Check each option
{ "bool": { "must": [ { "term": { "category": "books" } }, { "range": { "price": { "lt": 20 } } } ], "must_not": [ { "term": { "stock": "out" } } ] } } correctly usesmustarray for required conditions andmust_notarray for exclusion. { "bool": { "filter": [ { "term": { "category": "books" } }, { "range": { "price": { "lt": 20 } } } ], "must_not": { "term": { "stock": "out" } } } } usesfilterwhich is okay butmust_notis an object, not array. { "bool": { "should": [ { "term": { "category": "books" } }, { "range": { "price": { "lt": 20 } } } ], "must_not": [ { "term": { "stock": "out" } } ] } } usesshouldwhich makes conditions optional, wrong here. { "bool": { "must": { "term": { "category": "books" } }, "filter": { "range": { "price": { "lt": 20 } } }, "must_not": [ { "term": { "stock": "out" } } ] } } usesmustas object andfilteras object, mixing styles incorrectly.Final Answer:
{ "bool": { "must": [ { "term": { "category": "books" } }, { "range": { "price": { "lt": 20 } } } ], "must_not": [ { "term": { "stock": "out" } } ] } } -> Option CQuick Check:
Must array + must_not array for exclusion [OK]
- Using should instead of must for required filters
- Using object instead of array for must or must_not
- Mixing filter and must incorrectly
Ready to prove it?
Pass the test and this pattern moves unknown
