Tokenizers (standard, whitespace, pattern) in Elasticsearch - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of Standard Tokenizer on a Sample Text

Given the following Elasticsearch analyzer configuration using the standard tokenizer, what is the output tokens for the input text "Hello, world! This is Elasticsearch."?

Elasticsearch

{
  "analyzer": {
    "my_standard_analyzer": {
      "tokenizer": "standard"
    }
  }
}

Input text: "Hello, world! This is Elasticsearch."

A ["hello,", "world!", "this", "is", "elasticsearch."]

B ["Hello,", "world!", "This", "is", "Elasticsearch."]

C ["Hello", "world", "This", "is", "Elasticsearch"]

D ["hello", "world", "this", "is", "elasticsearch"]

💡 Hint

The standard tokenizer splits text into words by removing most punctuation and preserves case.

The standard tokenizer breaks text into words by removing most punctuation and preserves the original case of tokens.

❓ Predict Output

intermediate

Whitespace Tokenizer Output for a Given Text

What tokens does the whitespace tokenizer produce for the input text "Quick brown fox jumps over the lazy dog."?

Elasticsearch

{
  "analyzer": {
    "my_whitespace_analyzer": {
      "tokenizer": "whitespace"
    }
  }
}

Input text: "Quick brown fox jumps over the lazy dog."

A ]".god" ,"yzal" ,"eht" ,"revo" ,"spmuj" ,"xof" ,"nworb" ,"kciuQ"[

B ["Quick", "brown", "fox", "jumps", "over", "the", "lazy", "dog."]

C ["Quick", "brown", "fox", "jumps", "over", "the", "lazy", "dog"]

D ["quick", "brown", "fox", "jumps", "over", "the", "lazy", "dog"]

💡 Hint

Whitespace tokenizer splits tokens only on spaces and does not lowercase or remove punctuation.

The whitespace tokenizer splits text only on spaces, so punctuation remains attached to tokens and casing is preserved.

❓ Predict Output

advanced

Pattern Tokenizer with Custom Regex Output

Using the pattern tokenizer with the regex "\\W+" (non-word characters as delimiters), what tokens are produced from the input text "Email me at [e-mail]!"?

Elasticsearch

{
  "analyzer": {
    "my_pattern_analyzer": {
      "filter": ["lowercase"],
      "tokenizer": {
        "type": "pattern",
        "pattern": "\\W+"
      }
    }
  }
}

Input text: "Email me at [e-mail]!"

A ["email", "me", "at", "user", "example", "com"]

B ["Email", "me", "at", "[e-mail]"]

C ["email", "me", "at", "[e-mail]"]

D ["Email", "me", "at", "user", "example", "com"]

💡 Hint

The pattern tokenizer splits on non-word characters and lowercase filter converts tokens to lowercase.

The pattern tokenizer splits on any sequence of non-word characters (like @, ., !), so '[e-mail]' splits into 'user', 'example', 'com'. The lowercase filter makes all tokens lowercase.

❓ Predict Output

advanced

Effect of Pattern Tokenizer with Complex Regex

What tokens result from using a pattern tokenizer with the regex "[ ,.!]+" on the input text "Hello, world! Welcome to Elasticsearch."?

Elasticsearch

{
  "analyzer": {
    "complex_pattern_analyzer": {
      "tokenizer": {
        "type": "pattern",
        "pattern": "[ ,.!]+"
      }
    }
  }
}

Input text: "Hello, world! Welcome to Elasticsearch."

A ["Hello", "world", "Welcome", "to", "Elasticsearch"]

B ["Hello", "world!", "Welcome", "to", "Elasticsearch."]

C ["Hello", "world", "Welcome", "to", "Elasticsearch."]

D ["Hello,", "world", "Welcome", "to", "Elasticsearch"]

💡 Hint

The pattern tokenizer splits on any sequence of spaces, commas, periods, or exclamation marks.

The regex splits tokens on spaces, commas, periods, and exclamation marks, so punctuation is removed and tokens are split cleanly.

🧠 Conceptual

expert

Choosing the Correct Tokenizer for Case-Sensitive Search

You want to create an Elasticsearch analyzer that preserves the original casing of tokens and splits text only on whitespace. Which tokenizer should you use to achieve this?

A Use the <strong>standard</strong> tokenizer with a lowercase filter.

B Use the <strong>standard</strong> tokenizer without any filters.

C Use the <strong>pattern</strong> tokenizer with pattern "\\s+" and lowercase filter.

D Use the <strong>whitespace</strong> tokenizer without any filters.

💡 Hint

Think about which tokenizer splits only on spaces and does not change case by default.

The whitespace tokenizer splits tokens only on whitespace and does not lowercase tokens by default, preserving original casing. The standard tokenizer lowercases tokens by default. Pattern tokenizer can split on whitespace but often requires filters to preserve case.

Practice

1. Which Elasticsearch tokenizer splits text by spaces only, keeping punctuation as part of tokens?

easy

A. standard tokenizer

B. whitespace tokenizer

C. pattern tokenizer

D. keyword tokenizer

Solution

1. Step 1: Understand whitespace tokenizer behavior

   The whitespace tokenizer splits text only at spaces and keeps punctuation inside tokens.

2. Step 2: Compare with other tokenizers

   The standard tokenizer removes punctuation, and the pattern tokenizer splits by regex patterns, so they behave differently.

3. Final Answer:

   whitespace tokenizer -> Option B

4. Quick Check:

   Spaces split tokens only = whitespace tokenizer [OK]

Hint: Whitespace tokenizer splits only on spaces, keeps punctuation [OK]

Common Mistakes:

• Confusing standard tokenizer with whitespace tokenizer
• Thinking pattern tokenizer splits only on spaces
• Assuming keyword tokenizer splits text

2. Which of the following is the correct JSON syntax to define a pattern tokenizer that splits text on commas?

easy

A. { "tokenizer": "pattern", "pattern": ',' }

B. { 'tokenizer': 'pattern', 'pattern': ',' }

C. { "tokenizer": "pattern", pattern: "," }

D. { "tokenizer": "pattern", "pattern": "," }

Solution

1. Step 1: Identify correct JSON string escaping

   In JSON, double quotes inside strings must be escaped with a backslash, so the comma pattern must be inside escaped quotes.

2. Step 2: Check each option for proper escaping

   { "tokenizer": "pattern", "pattern": "," } correctly shows the pattern as a string with comma inside quotes.

3. Final Answer:

   { "tokenizer": "pattern", "pattern": "," } -> Option D

4. Quick Check:

   Proper JSON escaping for pattern string = { "tokenizer": "pattern", "pattern": "," } [OK]

Hint: Escape quotes inside JSON strings with backslash [OK]

Common Mistakes:

• Not escaping quotes inside JSON strings
• Using single quotes instead of double quotes
• Missing commas or braces in JSON

3. Given the text "Hello, world! Welcome to Elasticsearch.", what tokens does the standard tokenizer produce?

medium

A. ["Hello", "world!", "Welcome", "to", "Elasticsearch"]

B. ["Hello,", "world!", "Welcome", "to", "Elasticsearch."]

C. ["Hello", "world", "Welcome", "to", "Elasticsearch"]

D. ["Hello", "world", "Welcome", "to", "Elasticsearch."]

Solution

1. Step 1: Understand standard tokenizer behavior

   The standard tokenizer splits text by word boundaries and removes punctuation from tokens.

2. Step 2: Apply tokenizer to given text

   It splits "Hello," into "Hello", "world!" into "world", and removes punctuation marks like commas and exclamation points.

3. Final Answer:

   ["Hello", "world", "Welcome", "to", "Elasticsearch"] -> Option C

4. Quick Check:

   Standard tokenizer removes punctuation = ["Hello", "world", "Welcome", "to", "Elasticsearch"] [OK]

Hint: Standard tokenizer removes punctuation, returns clean words [OK]

Common Mistakes:

• Including punctuation in tokens with standard tokenizer
• Confusing output with whitespace tokenizer
• Assuming pattern tokenizer output without pattern

4. You defined a pattern tokenizer with pattern \W+ but it does not split the text as expected. What is the likely issue?

medium

A. The pattern is not properly escaped in JSON

B. Pattern tokenizer cannot use regex

C. Whitespace tokenizer should be used instead

D. Standard tokenizer must be enabled first

Solution

1. Step 1: Check pattern escaping in JSON

   Regex patterns with backslashes must be double escaped in JSON strings, so \W+ should be written as \\W+.

2. Step 2: Understand tokenizer requirements

   If pattern is not escaped properly, the tokenizer won't interpret it as intended, causing wrong splits.

3. Final Answer:

   The pattern is not properly escaped in JSON -> Option A

4. Quick Check:

   Regex backslash must be double escaped in JSON [OK]

Hint: Double escape backslashes in regex patterns for JSON [OK]

Common Mistakes:

• Using single backslash in JSON regex pattern
• Confusing tokenizer types
• Assuming pattern tokenizer needs enabling

5. You want to index a text field so that tokens are split on commas and semicolons only, keeping spaces and punctuation inside tokens. Which tokenizer configuration should you use?

hard

A. Use a pattern tokenizer with pattern [,;]

B. Use the standard tokenizer

C. Use the whitespace tokenizer

D. Use a pattern tokenizer with pattern \s+

Solution

1. Step 1: Identify tokenizer that splits on specific characters

   The pattern tokenizer allows splitting text by a custom regex pattern, so you can specify commas and semicolons.

2. Step 2: Confirm pattern matches commas and semicolons only

   The pattern [,;] matches commas or semicolons, splitting tokens at those characters but keeping spaces and other punctuation inside tokens.

3. Final Answer:

   Use a pattern tokenizer with pattern [,;] -> Option A

4. Quick Check:

   Pattern tokenizer with custom split chars = Use a pattern tokenizer with pattern [,;] [OK]

Hint: Pattern tokenizer splits by your regex pattern [OK]

Common Mistakes:

• Using whitespace tokenizer which splits on spaces
• Using standard tokenizer which removes punctuation
• Using wrong regex pattern for splitting