Analyzer components (tokenizer, filters) in Elasticsearch - Step-by-Step Execution

Concept Flow - Analyzer components (tokenizer, filters)

Input Text

↓

Tokenizer: splits text into tokens

↓

Filter 1: modifies tokens

↓

Filter 2: modifies tokens

↓

Output: final tokens for indexing/search

Text goes through a tokenizer to split it into words, then filters change these words step-by-step to prepare for search.

Execution Sample

Elasticsearch

POST _analyze
{
  "tokenizer": "standard",
  "filter": ["lowercase", "stop"],
  "text": "The Quick Brown Fox"
}

This example splits text into words, makes them lowercase, and removes common stop words.

Execution Table

Step	Action	Input Tokens	Output Tokens
1	Tokenizer splits text	["The Quick Brown Fox"]	["The", "Quick", "Brown", "Fox"]
2	Lowercase filter	["The", "Quick", "Brown", "Fox"]	["the", "quick", "brown", "fox"]
3	Stop filter removes stop words	["the", "quick", "brown", "fox"]	["quick", "brown", "fox"]
4	End of analysis	["quick", "brown", "fox"]	["quick", "brown", "fox"]

💡 All filters applied, final tokens ready for indexing/search.

Variable Tracker

Variable	Start	After Tokenizer	After Lowercase Filter	After Stop Filter	Final
tokens	N/A	["The", "Quick", "Brown", "Fox"]	["the", "quick", "brown", "fox"]	["quick", "brown", "fox"]	["quick", "brown", "fox"]

Key Moments - 2 Insights

Why does the token list change after each filter?

Each filter modifies the tokens step-by-step, as shown in execution_table rows 2 and 3, changing case or removing words.

Why is 'The' removed after the stop filter?

'The' is a common stop word removed by the stop filter, as seen in execution_table row 3 where it disappears from tokens.

Visual Quiz - 3 Questions

Look at the execution_table, what tokens are output after the lowercase filter (step 2)?

A ["The", "Quick", "Brown", "Fox"]

B ["the", "quick", "brown", "fox"]

C ["quick", "brown", "fox"]

D ["THE", "QUICK", "BROWN", "FOX"]

💡 Hint

Check the Output Tokens column at step 2 in execution_table.

At which step are stop words removed from the tokens?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look for the step where tokens like 'the' disappear in execution_table.

If we remove the lowercase filter, what would be the output tokens after the stop filter?

A ["Quick", "Brown", "Fox"]

B ["the", "quick", "brown", "fox"]

C ["The", "Quick", "Brown", "Fox"]

D ["quick", "brown", "fox"]

💡 Hint

Without lowercase filter, stop filter does not remove 'The' due to case sensitivity, leaving ["The", "Quick", "Brown", "Fox"].

Concept Snapshot

Analyzer components process text in steps:
1. Tokenizer splits text into words.
2. Filters modify tokens (e.g., lowercase, remove stop words).
3. Final tokens are used for search indexing.
Each filter changes tokens step-by-step.

Full Transcript

In Elasticsearch, an analyzer breaks text into tokens using a tokenizer, then applies filters to modify these tokens. For example, the standard tokenizer splits 'The Quick Brown Fox' into ['The', 'Quick', 'Brown', 'Fox']. Then the lowercase filter changes them to ['the', 'quick', 'brown', 'fox']. Next, the stop filter removes common words like 'the', resulting in ['quick', 'brown', 'fox']. This step-by-step process prepares text for efficient searching.

Practice

1. What is the main role of a tokenizer in an Elasticsearch analyzer?

easy

A. To remove stop words from the text

B. To split text into smaller pieces called tokens

C. To convert tokens to lowercase

D. To index the tokens for searching

Solution

1. Step 1: Understand the tokenizer's function

   A tokenizer breaks the input text into smaller parts called tokens, which are the basic units for searching.

2. Step 2: Differentiate tokenizer from filters

   Filters modify tokens after tokenization, such as lowercasing or removing stop words, but tokenizers do the initial splitting.

3. Final Answer:

   To split text into smaller pieces called tokens -> Option B

4. Quick Check:

   Tokenizer = splits text [OK]

Hint: Tokenizer always splits text into tokens first [OK]

Common Mistakes:

• Confusing tokenizer with filters like lowercase or stop word removal
• Thinking tokenizer indexes tokens
• Assuming tokenizer modifies tokens after splitting

2. Which of the following is the correct syntax to define a standard tokenizer in an Elasticsearch analyzer settings?

easy

A. "tokenizer": standard

B. "tokenizer": ["standard"]

C. "tokenizer": { "type": "standard" }

D. "tokenizer": { "name": "standard" }

Solution

1. Step 1: Recall Elasticsearch tokenizer syntax

   Tokenizers are defined as objects with a type field specifying the tokenizer type.

2. Step 2: Compare options

   "tokenizer": { "type": "standard" } correctly uses an object with type key, while others use incorrect formats like strings or arrays.

3. Final Answer:

   "tokenizer": { "type": "standard" } -> Option C

4. Quick Check:

   Tokenizer syntax uses type key in object [OK]

Hint: Tokenizer must be an object with type key [OK]

Common Mistakes:

• Using string directly instead of object with type
• Using array syntax for tokenizer
• Using incorrect key names like name instead of type

3. Given this analyzer configuration snippet:

{
  "tokenizer": "whitespace",
  "filter": ["lowercase", "stop"]
}

What will be the output tokens for the input text: "The Quick Brown Fox"?

medium

A. ["quick", "brown", "fox"]

B. ["The", "Quick", "Brown", "Fox"]

C. ["quick", "brown"]

D. ["the", "quick", "brown", "fox"]

Solution

1. Step 1: Apply the whitespace tokenizer

   The whitespace tokenizer splits text by spaces, so tokens are ["The", "Quick", "Brown", "Fox"].

2. Step 2: Apply lowercase and stop filters

   The lowercase filter converts all tokens to lowercase: ["the", "quick", "brown", "fox"]. The stop filter removes common stop words like "the", leaving ["quick", "brown", "fox"].

3. Final Answer:

   ["quick", "brown", "fox"] -> Option A

4. Quick Check:

   Lowercase + stop filter removes "the" [OK]

Hint: Stop filter removes common words after lowercase [OK]

Common Mistakes:

• Ignoring stop word removal
• Not applying lowercase filter before stop filter
• Assuming tokenizer changes case

4. Identify the error in this analyzer filter configuration:

{
  "filter": [
    { "type": "lowercase" },
    { "type": "stop", "stopwords": "_english_" },
    { "type": "unknown_filter" }
  ]
}

medium

A. Filters cannot be defined as objects

B. The lowercase filter must be a string, not an object

C. The stop filter syntax is incorrect

D. The filter list contains an invalid filter type

Solution

1. Step 1: Review each filter type

   Lowercase and stop filters are valid and correctly defined. The stop filter uses a valid stopwords parameter.

2. Step 2: Identify invalid filter

   The filter with type "unknown_filter" is not a valid Elasticsearch filter type and will cause an error.

3. Final Answer:

   The filter list contains an invalid filter type -> Option D

4. Quick Check:

   Invalid filter type causes error [OK]

Hint: Check filter types are valid Elasticsearch filters [OK]

Common Mistakes:

• Assuming all filter types are valid
• Thinking lowercase filter must be string
• Ignoring unknown filter errors

5. You want to create a custom analyzer that splits text on whitespace, lowercases tokens, and removes English stop words. Which of the following analyzer settings is correct?

hard

A. { "tokenizer": { "type": "whitespace" }, "filter": ["lowercase", { "type": "stop", "stopwords": "_english_" }] }

B. { "tokenizer": "whitespace", "filter": ["lowercase", stop] }

C. { "tokenizer": "standard", "filter": ["lowercase", "stop"] }

D. { "tokenizer": { "type": "whitespace" }, "filter": ["stop", "lowercase"] }

Solution

1. Step 1: Confirm tokenizer type

   The tokenizer must be whitespace type, correctly defined as an object with type "whitespace".

2. Step 2: Confirm filter order and definition

   Filters should lowercase first, then remove stop words. { "tokenizer": { "type": "whitespace" }, "filter": ["lowercase", { "type": "stop", "stopwords": "_english_" }] } correctly defines lowercase as string and stop filter with explicit stopwords parameter.

3. Step 3: Check other options

   { "tokenizer": "whitespace", "filter": ["lowercase", "stop"] } uses tokenizer as string which is allowed but less explicit; { "tokenizer": "standard", "filter": ["lowercase", "stop"] } uses standard tokenizer which is incorrect; { "tokenizer": { "type": "whitespace" }, "filter": ["stop", "lowercase"] } reverses filter order which may affect results.

4. Final Answer:

   { "tokenizer": { "type": "whitespace" }, "filter": ["lowercase", { "type": "stop", "stopwords": "_english_" }] } -> Option A

5. Quick Check:

   Explicit tokenizer and correct filter order [OK]

Hint: Use object for tokenizer and correct filter order [OK]

Common Mistakes:

• Using wrong tokenizer type
• Reversing filter order
• Not specifying stopwords explicitly