Search-as-you-type field in Elasticsearch - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Elasticsearch search-as-you-type query?

Given the following mapping and query, what will be the total number of hits returned?

Elasticsearch

{
  "mappings": {
    "properties": {
      "title": {
        "type": "search_as_you_type"
      }
    }
  }
}

POST /books/_search
{
  "query": {
    "match": {
      "title": {
        "query": "harry pot",
        "operator": "and"
      }
    }
  }
}

A The query returns all documents containing both 'harry' and 'pot' in the title field.

B The query returns documents containing the exact phrase 'harry pot' only.

C The query returns documents containing either 'harry' or 'pot' in the title field.

D The query returns no documents because 'pot' is incomplete.

💡 Hint

Consider how the 'operator': 'and' affects the match query with search_as_you_type fields.

The 'search_as_you_type' field indexes prefixes of words, so partial terms like 'pot' match 'potter'. Using 'operator': 'and' requires both terms to be present in the document, but they can be partial matches.

🧠 Conceptual

intermediate

Which Elasticsearch field type is best suited for implementing search-as-you-type functionality?

You want to enable users to get instant search suggestions as they type partial words. Which field type should you use in your mapping?

A "search_as_you_type"

B "keyword" with normalizer

C "text" with standard analyzer

D "completion"

💡 Hint

Think about which field type indexes prefixes of words for partial matching.

The 'search_as_you_type' field type is designed to index prefixes of words to support efficient search-as-you-type queries.

🔧 Debug

advanced

Why does this search-as-you-type query return zero results?

Given this mapping and query, why does the search return no hits? Mapping: { "properties": { "name": { "type": "search_as_you_type" } } } Query: { "query": { "match": { "name": "j" } } }

A The query is missing the 'operator': 'and' parameter.

B The query string 'j' is too short to match any indexed prefix.

C The 'match' query does not work with 'search_as_you_type' fields; a 'multi_match' is required.

D The field 'name' is not analyzed, so partial matches fail.

💡 Hint

Consider the minimum prefix length indexed by default in 'search_as_you_type'.

By default, 'search_as_you_type' indexes prefixes starting from length 2, so a 1-letter query like 'j' does not match any prefix.

📝 Syntax

advanced

Which query syntax correctly searches a search_as_you_type field for partial input 'prog'?

Select the valid Elasticsearch query that searches the 'title' field of type 'search_as_you_type' for the prefix 'prog'.

A { "match": { "title": "prog" } }

B { "prefix": { "title": "prog" } }

C { "match_phrase_prefix": { "title": "prog" } }

D { "term": { "title": "prog" } }

💡 Hint

Which query type supports prefix matching on analyzed fields?

The 'match_phrase_prefix' query supports prefix matching on analyzed fields like 'search_as_you_type'. 'prefix' query works only on keyword fields, and 'term' requires exact match.

🚀 Application

expert

How to optimize search-as-you-type for multi-word inputs with Elasticsearch?

You want to implement a search-as-you-type feature that handles multi-word inputs efficiently, such as 'data scie'. Which approach is best to achieve accurate prefix matching on each word?

A Use a single 'search_as_you_type' field and query it with 'match' on the full input string.

B Use multiple 'search_as_you_type' fields for each word and combine queries with 'bool' must clauses.

C Use a 'completion' field with prefix queries for each word separately.

D Use a 'search_as_you_type' field and query with 'multi_match' type 'bool_prefix' to match prefixes of multiple words.

💡 Hint

Consider which query type supports prefix matching on multiple words in a single field.

The 'multi_match' query with type 'bool_prefix' is designed to efficiently match prefixes of multiple words in a 'search_as_you_type' field, improving multi-word search-as-you-type experience.

Practice

1. What is the main purpose of a search_as_you_type field in Elasticsearch?

easy

A. To provide instant search results as the user types each character

B. To store large binary files efficiently

C. To perform complex aggregations on numeric data

D. To index documents only after full text is entered

Solution

1. Step 1: Understand the purpose of search_as_you_type

   The search_as_you_type field is designed to help users get search results instantly as they type, improving user experience.

2. Step 2: Compare with other options

   Options B, C, and D describe unrelated Elasticsearch features like binary storage, aggregations, or delayed indexing, which are not related to search_as_you_type.

3. Final Answer:

   To provide instant search results as the user types each character -> Option A

4. Quick Check:

   search_as_you_type = instant search while typing [OK]

Hint: Remember: search_as_you_type means live search suggestions [OK]

Common Mistakes:

• Confusing search_as_you_type with binary or numeric fields
• Thinking it delays indexing until full input
• Assuming it is for aggregations

2. Which is the correct way to define a search_as_you_type field in an Elasticsearch mapping?

easy

A. "title": { "type": "text" }

B. "title": { "type": "completion" }

C. "title": { "type": "keyword" }

D. "title": { "type": "search_as_you_type" }

Solution

1. Step 1: Identify the correct field type for search-as-you-type

   The search_as_you_type field type must be explicitly set as "type": "search_as_you_type" in the mapping.

2. Step 2: Eliminate other field types

   "title": { "type": "text" } uses text, which is for full text search but not optimized for search-as-you-type. "title": { "type": "keyword" } uses keyword, which is for exact matches. "title": { "type": "completion" } uses completion, which is for autocomplete but different from search_as_you_type.

3. Final Answer:

   "title": { "type": "search_as_you_type" } -> Option D

4. Quick Check:

   Mapping type for search-as-you-type = search_as_you_type [OK]

Hint: Use type "search_as_you_type" exactly in mapping [OK]

Common Mistakes:

• Using "text" instead of "search_as_you_type"
• Confusing with "completion" type
• Omitting the type field

3. Given this mapping snippet:

{
  "mappings": {
    "properties": {
      "name": { "type": "search_as_you_type" }
    }
  }
}

Which query will correctly search for documents where the name field starts with "mic"?

medium

A. { "match": { "name": "mic" } }

B. { "multi_match": { "query": "mic", "type": "bool_prefix", "fields": ["name", "name._2gram", "name._3gram"] } }

C. { "term": { "name": "mic" } }

D. { "prefix": { "name": "mic" } }

Solution

1. Step 1: Understand how to query search_as_you_type fields

   Search-as-you-type fields require a multi_match query with type: bool_prefix and fields including the base field and its n-gram subfields.

2. Step 2: Analyze each query option

   { "match": { "name": "mic" } } uses simple match, which does not support prefix matching well. { "term": { "name": "mic" } } uses term query, which requires exact match. { "prefix": { "name": "mic" } } uses prefix query, which is not optimized for search_as_you_type. { "multi_match": { "query": "mic", "type": "bool_prefix", "fields": ["name", "name._2gram", "name._3gram"] } } correctly uses multi_match with bool_prefix and the required fields.

3. Final Answer:

   { "multi_match": { "query": "mic", "type": "bool_prefix", "fields": ["name", "name._2gram", "name._3gram"] } } -> Option B

4. Quick Check:

   Use multi_match + bool_prefix + ngram fields [OK]

Hint: Use multi_match with bool_prefix and ngram fields [OK]

Common Mistakes:

• Using term or prefix queries alone
• Not including ngram subfields in fields list
• Using simple match query for prefix search

4. You wrote this query to search a search_as_you_type field but get no results:

{ "multi_match": { "query": "app", "type": "bool_prefix", "fields": ["title"] } }

What is the likely problem?

medium

A. The field 'title' must be of type 'keyword' for this query

B. The 'bool_prefix' type is invalid for multi_match queries

C. The query should include ngram subfields like 'title._2gram' and 'title._3gram'

D. The query string 'app' is too short to match anything

Solution

1. Step 1: Check query fields for search_as_you_type

   Search-as-you-type fields generate subfields with ngrams like '_2gram' and '_3gram' that must be included in the query fields for prefix matching.

2. Step 2: Identify missing ngram subfields in the query

   The query only searches 'title' field, missing 'title._2gram' and 'title._3gram', so it won't match prefixes properly.

3. Final Answer:

   The query should include ngram subfields like 'title._2gram' and 'title._3gram' -> Option C

4. Quick Check:

   Include ngram subfields in fields list for prefix search [OK]

Hint: Always add _2gram and _3gram subfields in multi_match fields [OK]

Common Mistakes:

• Omitting ngram subfields in fields list
• Thinking bool_prefix is invalid
• Assuming keyword type is needed
• Blaming query length

5. You want to implement a search-as-you-type feature for a product catalog with a name field. Which of the following mapping and query combinations will correctly support prefix matching as the user types?

hard

A. Mapping: { "name": { "type": "search_as_you_type" } }Query: { "multi_match": { "query": "lap", "type": "bool_prefix", "fields": ["name", "name._2gram", "name._3gram"] } }

B. Mapping: { "name": { "type": "text" } }Query: { "match": { "name": "lap" } }

C. Mapping: { "name": { "type": "keyword" } }Query: { "prefix": { "name": "lap" } }

D. Mapping: { "name": { "type": "completion" } }Query: { "term": { "name": "lap" } }

Solution

1. Step 1: Choose the correct mapping for search-as-you-type

   The search_as_you_type type is designed for prefix matching and instant search as the user types.

2. Step 2: Use the correct query for prefix matching

   The multi_match query with bool_prefix type and fields including the base field and its ngram subfields is required for effective prefix matching.

3. Step 3: Evaluate other options

   Mapping: { "name": { "type": "text" } }
   Query: { "match": { "name": "lap" } } uses text with simple match, which does not support prefix search well. Mapping: { "name": { "type": "keyword" } }
   Query: { "prefix": { "name": "lap" } } uses keyword with prefix query, which is less flexible. Mapping: { "name": { "type": "completion" } }
   Query: { "term": { "name": "lap" } } uses completion with term query, which is incorrect usage.

4. Final Answer:

   Mapping: { "name": { "type": "search_as_you_type" } } and Query: { "multi_match": { "query": "lap", "type": "bool_prefix", "fields": ["name", "name._2gram", "name._3gram"] } } -> Option A

5. Quick Check:

   search_as_you_type + multi_match bool_prefix + ngram fields = correct [OK]

Hint: Combine search_as_you_type mapping with multi_match bool_prefix query [OK]

Common Mistakes:

• Using text type with match query for prefix search
• Using keyword type with prefix query only
• Confusing completion type with search_as_you_type
• Using term query for prefix matching