Bird
Raised Fist0
Elasticsearchquery~30 mins

Object and nested types in Elasticsearch - Mini Project: Build & Apply

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime
Working with Object and Nested Types in Elasticsearch
📖 Scenario: You are building a search index for an online bookstore. Each book has details like title, author, and a list of reviews. Each review has a reviewer name and a rating. You want to store this data in Elasticsearch using object and nested types to keep the reviews structured.
🎯 Goal: Create an Elasticsearch index mapping that uses object type for the author details and nested type for the list of reviews. Then, add a sample document with one book, its author, and two reviews.
📋 What You'll Learn
Create an index mapping named books with author as an object type
Define reviews as a nested type with fields reviewer (text) and rating (integer)
Index a sample document with title, author details, and two reviews
Print the indexed document to verify the structure
💡 Why This Matters
🌍 Real World
Online bookstores and review platforms often store complex data with nested relationships. Using object and nested types in Elasticsearch helps keep this data organized and searchable.
💼 Career
Understanding how to model nested data in Elasticsearch is important for roles like backend developers, data engineers, and search specialists who build scalable search applications.
Progress0 / 4 steps
1
Create the index mapping with object and nested types
Create an index mapping called books with a properties field. Inside properties, define author as an object type with fields name (text) and birth_year (integer). Also, define reviews as a nested type with fields reviewer (text) and rating (integer). Write the JSON mapping exactly as shown.
Elasticsearch
Hint

Remember to nest the name and birth_year fields inside the author object, and the reviewer and rating fields inside the reviews nested type.

2
Add a sample book document with author and reviews
Create a JSON document called book_doc with these exact fields: title as "The Great Adventure", author as an object with name "John Smith" and birth_year 1975, and reviews as a list of two nested objects: first with reviewer "Alice" and rating 5, second with reviewer "Bob" and rating 4.
Elasticsearch
Hint

Make sure the author is an object with the exact fields, and reviews is a list of nested objects with the correct reviewer names and ratings.

3
Index the sample document into the books index
Write a command to index the book_doc document into the books index using the Elasticsearch Python client syntax: es.index(index="books", document=book_doc). Assign the result to a variable called response.
Elasticsearch
Hint

Use the es.index method with the index parameter set to "books" and the document parameter set to book_doc. Assign the result to response.

4
Print the indexed document to verify
Write a print statement to display the book_doc variable so you can see the full document structure.
Elasticsearch
Hint

Use print(book_doc) to display the document. The output should show the full nested structure.

Practice

(1/5)
1. What is the main difference between object and nested types in Elasticsearch?
easy
A. Both types store data the same way but nested type is faster.
B. Object type stores arrays of objects separately, while nested type stores grouped fields as one JSON object.
C. Nested type is used only for numeric fields, object type for text fields.
D. Nested type stores arrays of objects separately to keep their fields linked during searches, while object type stores grouped fields as one JSON object.

Solution

  1. Step 1: Understand object type storage

    Object type stores grouped fields as a single JSON object inside a document, meaning all fields are flattened and stored together.

  2. Step 2: Understand nested type storage

    Nested type stores arrays of objects separately to maintain the relationship between fields within each object during searches.

  3. Final Answer:

    Nested type stores arrays of objects separately to keep their fields linked during searches, while object type stores grouped fields as one JSON object. -> Option D

  4. Quick Check:

    Nested keeps object fields linked = C [OK]
Hint: Nested keeps object arrays linked; object flattens fields [OK]
Common Mistakes:
  • Confusing object and nested storage behavior
  • Thinking nested is only for numeric fields
  • Assuming both types store data the same way
2. Which of the following is the correct way to define a nested type field in an Elasticsearch mapping?
easy
A. "comments": { "type": "object" }
B. "comments": { "type": "keyword" }
C. "comments": { "type": "nested" }
D. "comments": { "type": "text" }

Solution

  1. Step 1: Recall nested type syntax

    To define a nested field, the type must be explicitly set to "nested" in the mapping.

  2. Step 2: Check options

    "comments": { "type": "nested" } correctly sets "comments" field type to "nested". Other options use incorrect types for nested data.

  3. Final Answer:

    "comments": { "type": "nested" } -> Option C

  4. Quick Check:

    Nested type requires "type": "nested" [OK]
Hint: Use "type": "nested" to define nested fields [OK]
Common Mistakes:
  • Using "object" instead of "nested" for nested arrays
  • Confusing text or keyword types with nested
  • Omitting the type field
3. Given this mapping with a nested field comments and this document:
{"title": "Post", "comments": [{"user": "alice", "message": "Hi"}, {"user": "bob", "message": "Hello"}]}

Which query will correctly find documents where comments.user is "alice" and comments.message is "Hello" in the same comment object?
medium
A. { "query": { "nested": { "path": "comments", "query": { "bool": { "must": [ { "match": { "comments.user": "alice" } }, { "match": { "comments.message": "Hello" } } ] } } } } }
B. { "query": { "bool": { "must": [ { "match": { "comments.user": "alice" } }, { "match": { "comments.message": "Hello" } } ] } } }
C. { "query": { "term": { "comments.user": "alice" } } }
D. { "query": { "nested": { "path": "comments", "query": { "term": { "comments.message": "Hi" } } } } }

Solution

  1. Step 1: Understand nested query usage

    To search inside nested fields and keep field relationships, use a nested query with the correct path and combined conditions inside it.

  2. Step 2: Analyze options

    { "query": { "nested": { "path": "comments", "query": { "bool": { "must": [ { "match": { "comments.user": "alice" } }, { "match": { "comments.message": "Hello" } } ] } } } } } uses a nested query on "comments" with a bool must for both user "alice" and message "Hello" in the same nested object. { "query": { "bool": { "must": [ { "match": { "comments.user": "alice" } }, { "match": { "comments.message": "Hello" } } ] } } } searches flattened fields, losing the link. { "query": { "term": { "comments.user": "alice" } } } only matches user. { "query": { "nested": { "path": "comments", "query": { "term": { "comments.message": "Hi" } } } } } searches for message "Hi" only.

  3. Final Answer:

    Uses nested query to match both conditions in the same nested object. -> Option A

  4. Quick Check:

    Nested query with bool must inside = A [OK]
Hint: Use nested query with bool must for multiple nested conditions [OK]
Common Mistakes:
  • Using bool query without nested for nested fields
  • Searching fields separately losing object linkage
  • Using term query without nested path
4. You wrote this mapping for a nested field:
{ "properties": { "tags": { "type": "nested", "properties": { "name": { "type": "keyword" } } } } }

But your nested query returns no results even though documents have matching tags. What is the likely mistake?
medium
A. You forgot to use a nested query; used a regular bool query instead.
B. You defined tags as object type instead of nested.
C. You used match query on keyword field instead of term query.
D. You indexed tags as text instead of keyword.

Solution

  1. Step 1: Check mapping correctness

    The mapping correctly defines "tags" as nested with keyword "name" field, so mapping is fine.

  2. Step 2: Identify query mistake

    If nested query returns no results, often the cause is using a regular bool query instead of a nested query to search nested fields, losing the link between nested objects.

  3. Final Answer:

    You forgot to use a nested query; used a regular bool query instead. -> Option A

  4. Quick Check:

    Nested fields require nested queries [OK]
Hint: Always use nested query for nested fields [OK]
Common Mistakes:
  • Using bool query without nested for nested fields
  • Confusing object and nested types in mapping
  • Using match query on keyword fields
5. You have documents with a nested field orders containing product and quantity. You want to find documents where there is an order with product "apple" and quantity greater than 10, but also an order with product "banana" and quantity less than 5. Which query structure correctly finds such documents?
hard
A. { "query": { "nested": { "path": "orders", "query": { "bool": { "must": [ { "term": { "orders.product": "apple" } }, { "range": { "orders.quantity": { "gt": 10 } } }, { "term": { "orders.product": "banana" } }, { "range": { "orders.quantity": { "lt": 5 } } } ] } } } }
B. { "query": { "bool": { "must": [ { "nested": { "path": "orders", "query": { "bool": { "must": [ { "term": { "orders.product": "apple" } }, { "range": { "orders.quantity": { "gt": 10 } } } ] } } } }, { "nested": { "path": "orders", "query": { "bool": { "must": [ { "term": { "orders.product": "banana" } }, { "range": { "orders.quantity": { "lt": 5 } } } ] } } } } ] } } }
C. { "query": { "bool": { "must": [ { "term": { "orders.product": "apple" } }, { "range": { "orders.quantity": { "gt": 10 } } }, { "term": { "orders.product": "banana" } }, { "range": { "orders.quantity": { "lt": 5 } } } ] } } }
D. { "query": { "nested": { "path": "orders", "query": { "term": { "orders.product": "apple" } } } } }

Solution

  1. Step 1: Understand nested query for multiple conditions

    Each nested object must be queried separately to keep conditions linked inside the same nested object.

  2. Step 2: Analyze query options

    { "query": { "bool": { "must": [ { "nested": { "path": "orders", "query": { "bool": { "must": [ { "term": { "orders.product": "apple" } }, { "range": { "orders.quantity": { "gt": 10 } } } ] } } } }, { "nested": { "path": "orders", "query": { "bool": { "must": [ { "term": { "orders.product": "banana" } }, { "range": { "orders.quantity": { "lt": 5 } } } ] } } } } ] } } } uses two nested queries combined with bool must, one for "apple" orders with quantity > 10, another for "banana" orders with quantity < 5, correctly matching documents with both conditions in different nested objects.

  3. Step 3: Identify incorrect options

    { "query": { "nested": { "path": "orders", "query": { "bool": { "must": [ { "term": { "orders.product": "apple" } }, { "range": { "orders.quantity": { "gt": 10 } } }, { "term": { "orders.product": "banana" } }, { "range": { "orders.quantity": { "lt": 5 } } } ] } } } } tries to combine all conditions in one nested query, which requires all conditions in the same nested object (impossible for different products). { "query": { "bool": { "must": [ { "term": { "orders.product": "apple" } }, { "range": { "orders.quantity": { "gt": 10 } } }, { "term": { "orders.product": "banana" } }, { "range": { "orders.quantity": { "lt": 5 } } } ] } } } ignores nested queries, losing object linkage. { "query": { "nested": { "path": "orders", "query": { "term": { "orders.product": "apple" } } } } } only queries for "apple" product.

  4. Final Answer:

    Uses separate nested queries for each product condition. -> Option B

  5. Quick Check:

    Separate nested queries for each condition = A [OK]
Hint: Use separate nested queries for different nested object conditions [OK]
Common Mistakes:
  • Combining multiple product conditions in one nested query
  • Not using nested queries for nested fields
  • Assuming all conditions apply to the same nested object
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard