Why mappings define document structure in Elasticsearch - Challenge Your Understanding

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this mapping definition?

Given this Elasticsearch mapping snippet, what will be the data type of the field age in the index?

Elasticsearch

{
  "mappings": {
    "properties": {
      "name": { "type": "text" },
      "age": { "type": "integer" }
    }
  }
}

A "age" will be treated as a string field.

B "age" will be treated as an integer field.

C "age" will be treated as a date field.

D "age" will be treated as a boolean field.

💡 Hint

Look at the type assigned to the "age" field inside the mapping.

Mappings define the data types of fields in Elasticsearch. Here, "age" is explicitly set as "integer", so Elasticsearch will treat it as a number without decimals.

🧠 Conceptual

intermediate

Why do mappings matter in Elasticsearch?

Why is it important to define mappings before indexing documents in Elasticsearch?

A Mappings are only used to store documents, not to search them.

B Mappings automatically fix errors in documents during indexing.

C Mappings allow Elasticsearch to know how to index and search each field correctly.

D Mappings slow down the indexing process and should be avoided.

💡 Hint

Think about how Elasticsearch uses mappings to understand data.

Mappings tell Elasticsearch the data type and structure of each field, so it can index and search data efficiently and correctly.

🔧 Debug

advanced

Identify the error in this mapping snippet

This mapping is intended to define a date field named created_at. What is wrong with it?

Elasticsearch

{
  "mappings": {
    "properties": {
      "created_at": { "type": "dates" }
    }
  }
}

A The type "dates" is invalid; it should be "date".

B The field name "created_at" is not allowed in mappings.

C The mapping is missing a "format" property for the date.

D There is no error; this mapping is correct.

💡 Hint

Check the spelling of the data type.

Elasticsearch expects the type to be "date" (singular). "dates" is not a valid type and will cause an error.

📝 Syntax

advanced

Which mapping snippet is syntactically correct?

Choose the mapping snippet that is valid JSON and correctly defines a nested field address with city and zipcode as text fields.

A { "mappings": { "properties": { "address": { "type": "nested", "properties": { "city": { "type": "text" }, "zipcode": { "type": "text" } } } } } }

B { "mappings": { "properties": { "address": { "nested": true, "fields": { "city": "text", "zipcode": "text" } } } } }

C { "mappings": { "properties": { "address": { "type": "object", "city": { "type": "text" }, "zipcode": { "type": "text" } } } } }

D { "mappings": { "properties": { "address": { "type": "nested", "city": { "type": "text" }, "zipcode": { "type": "text" } } } } }

💡 Hint

Look for the correct use of "type": "nested" and the "properties" keyword.

Option A correctly uses "type": "nested" and nests the "city" and "zipcode" fields inside "properties". Other options misuse keywords or structure.

🚀 Application

expert

How many fields will be indexed in this mapping?

Given this mapping, how many fields will Elasticsearch index for each document?

Elasticsearch

{
  "mappings": {
    "properties": {
      "user": {
        "properties": {
          "name": { "type": "text" },
          "email": { "type": "keyword" }
        }
      },
      "tags": { "type": "keyword" },
      "comments": {
        "type": "nested",
        "properties": {
          "author": { "type": "text" },
          "message": { "type": "text" }
        }
      }
    }
  }
}

A 6 fields

B 4 fields

C 3 fields

D 5 fields

💡 Hint

Count all leaf fields inside properties, including nested ones.

The fields are: user.name, user.email, tags, comments.author, comments.message. Total 5 fields indexed.