Sorting results in Elasticsearch - Step-by-Step Execution

Concept Flow - Sorting results

Receive search query

↓

Parse query and sort parameters

↓

Execute search on index

↓

Sort results by specified field(s)

↓

Return sorted results to user

The search query is received and parsed, then the results are sorted by the specified field(s) before returning.

Execution Sample

Elasticsearch

{
  "query": { "match_all": {} },
  "sort": [ { "price": { "order": "asc" } } ]
}

This query fetches all documents and sorts them by the 'price' field in ascending order.

Execution Table

Step	Action	Sort Field	Sort Order	Result Order (IDs)
1	Receive query	-	-	-
2	Parse query and sort	price	asc	-
3	Execute search	-	-	[doc1, doc2, doc3, doc4] (unsorted)
4	Sort results by price ascending	price	asc	[doc3 (10), doc1 (20), doc4 (30), doc2 (40)]
5	Return sorted results	-	-	[doc3, doc1, doc4, doc2]

💡 All documents sorted by price ascending and returned.

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
query	null	{"match_all":{}}	{"match_all":{}}	{"match_all":{}}
sort	null	[{"price":{"order":"asc"}}]	[{"price":{"order":"asc"}}]	[{"price":{"order":"asc"}}]
results	null	[doc1(20), doc2(40), doc3(10), doc4(30)]	[doc3(10), doc1(20), doc4(30), doc2(40)]	[doc3(10), doc1(20), doc4(30), doc2(40)]

Key Moments - 2 Insights

Why do the results change order only after step 4?

Because the search execution (step 3) returns unsorted results, and only at step 4 does the sorting by the specified field happen, changing the order.

What happens if no sort parameter is given?

If no sort is specified, Elasticsearch returns results in its default relevance order, so no explicit sorting step occurs as shown in the table.

Visual Quiz - 3 Questions

Look at the execution table, what is the order of document IDs after step 4?

A [doc2, doc4, doc1, doc3]

B [doc3, doc1, doc4, doc2]

C [doc1, doc2, doc3, doc4]

D [doc4, doc3, doc2, doc1]

💡 Hint

Check the 'Result Order (IDs)' column at step 4 in the execution_table.

At which step does Elasticsearch parse the sort parameters?

A Step 3

B Step 1

C Step 2

D Step 5

💡 Hint

Look at the 'Action' column in the execution_table for parsing actions.

If the sort order changed to descending, how would the final order look?

A [doc2, doc4, doc1, doc3]

B [doc3, doc1, doc4, doc2]

C [doc1, doc2, doc3, doc4]

D [doc4, doc3, doc2, doc1]

💡 Hint

Descending order means highest price first; check the prices in variable_tracker.

Concept Snapshot

Sorting results in Elasticsearch:
- Use the 'sort' field in the query JSON.
- Specify field and order (asc or desc).
- Elasticsearch sorts results after search execution.
- Default is relevance if no sort given.
- Multiple fields can be used for sorting.

Full Transcript

This visual execution trace shows how Elasticsearch processes a search query with sorting. First, the query and sort parameters are received and parsed. Then the search executes, returning unsorted results. Next, Elasticsearch sorts these results by the specified field and order. Finally, the sorted results are returned to the user. Variables like 'query', 'sort', and 'results' change state through these steps. Key points include understanding when sorting happens and what default behavior is if no sort is specified. The quiz questions help reinforce these steps by referencing the execution table and variable states.

Practice

1. What does the sort parameter do in an Elasticsearch query?

easy

A. It arranges the search results in a specified order.

B. It filters the search results based on a condition.

C. It changes the index mapping settings.

D. It deletes documents from the index.

Solution

1. Step 1: Understand the purpose of sort

   The sort parameter is used to order search results by a field in ascending or descending order.

2. Step 2: Differentiate from other parameters

   Filtering narrows results, mapping changes structure, and deleting removes data, none of which are sorting.

3. Final Answer:

   It arranges the search results in a specified order. -> Option A

4. Quick Check:

   Sorting = arranging results [OK]

Hint: Sort means order your results by a field [OK]

Common Mistakes:

• Confusing sorting with filtering
• Thinking sort deletes or changes data
• Mixing sort with index settings

2. Which of the following is the correct syntax to sort results by the field price in descending order?

easy

A. "sort": [{"price": "desc"}]

B. "sort": {"price": "descending"}

C. "sort": ["price:desc"]

D. "sort": [{"price": "down"}]

Solution

1. Step 1: Check Elasticsearch sort syntax

   Sorting uses an array of objects with field name and order as "asc" or "desc" strings.

2. Step 2: Validate each option

   "sort": [{"price": "desc"}] uses correct JSON array and "desc" keyword. Others use invalid keywords or formats.

3. Final Answer:

   "sort": [{"price": "desc"}] -> Option A

4. Quick Check:

   Correct syntax uses array and "desc" [OK]

Hint: Use array with field and "asc" or "desc" strings [OK]

Common Mistakes:

• Using wrong keywords like "descending" or "down"
• Not using an array for sort
• Incorrect JSON object structure

3. Given this Elasticsearch query snippet, what is the order of the returned documents by age?

{
  "sort": [{"age": "asc"}]
}

medium

A. Documents are sorted from oldest to youngest.

B. Documents are sorted alphabetically by age.

C. Documents are sorted randomly.

D. Documents are sorted from youngest to oldest.

Solution

1. Step 1: Understand the meaning of "asc" in sorting

   "asc" means ascending order, so smaller values come first.

2. Step 2: Apply to the field "age"

   Sorting by age ascending means documents with lower age values appear before higher ones.

3. Final Answer:

   Documents are sorted from youngest to oldest. -> Option D

4. Quick Check:

   "asc" = ascending = smallest to largest [OK]

Hint: "asc" means smallest to largest values [OK]

Common Mistakes:

• Confusing "asc" with descending order
• Thinking sorting is random
• Assuming alphabetical sort on numbers

4. Identify the error in this Elasticsearch sort snippet:

{
  "sort": {"date": "asc"}
}

medium

A. Sort cannot be used with date fields.

B. Sort must be an array, not a single object.

C. Field name "date" must be inside quotes.

D. The order "asc" is invalid; should be "ascending".

Solution

1. Step 1: Check the required structure for sort

   Sort expects an array of objects, even if sorting by one field.

2. Step 2: Analyze the given snippet

   The snippet uses an object directly, missing the array brackets [].

3. Final Answer:

   Sort must be an array, not a single object. -> Option B

4. Quick Check:

   Sort = array of objects [OK]

Hint: Sort always uses an array, even for one field [OK]

Common Mistakes:

• Using object instead of array for sort
• Wrong order keywords like "ascending"
• Thinking sort can't be used on dates

5. You want to sort search results first by category alphabetically ascending, then by price descending. Which is the correct sort clause?

hard

A. "sort": {"category": "asc", "price": "desc"}

B. "sort": [{"price": "desc"}, {"category": "asc"}]

C. "sort": [{"category": "asc"}, {"price": "desc"}]

D. "sort": [{"category": "desc"}, {"price": "asc"}]

Solution

1. Step 1: Understand multi-level sorting order

   Sorting applies fields in order: first field sorts primary, second field breaks ties.

2. Step 2: Match required order

   First by category ascending, then by price descending means category asc first, price desc second.

3. Step 3: Validate syntax

   Sort must be an array of objects with field and order pairs.

4. Final Answer:

   "sort": [{"category": "asc"}, {"price": "desc"}] -> Option C

5. Quick Check:

   Primary asc category, secondary desc price [OK]

Hint: List sort fields in order inside array [OK]

Common Mistakes:

• Reversing sort order of fields
• Using object instead of array for multiple fields
• Mixing ascending and descending incorrectly