Why indexes organize data in Elasticsearch - Challenge Your Understanding

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Elasticsearch query?

Given an Elasticsearch index named products with documents containing fields name and price, what will this query return?

{
  "query": {
    "range": {
      "price": {
        "gte": 100,
        "lte": 200
      }
    }
  }
}

A All documents regardless of price

B Documents with price less than 100

C Documents with price greater than 200

D Documents with price between 100 and 200 inclusive

💡 Hint

Look at the range query and the meaning of gte and lte.

The range query filters documents where the price field is greater than or equal to 100 and less than or equal to 200.

🧠 Conceptual

intermediate

Why does Elasticsearch use indexes to organize data?

Choose the best explanation for why Elasticsearch organizes data into indexes.

A To prevent any data from being deleted accidentally

B To store data in a single large file for easy backup

C To speed up search by allowing quick lookups on specific fields

D To make data unreadable for security reasons

💡 Hint

Think about how indexes help find data fast.

Indexes in Elasticsearch organize data so searches can quickly find matching documents without scanning everything.

🔧 Debug

advanced

What error does this Elasticsearch mapping cause?

Given this mapping snippet, what error will Elasticsearch raise?

{
  "mappings": {
    "properties": {
      "price": {
        "type": "text"
      }
    }
  }
}

Assuming price should be a number.

A Search on price range queries will fail because price is text, not numeric

B Elasticsearch will accept the mapping without error

C Elasticsearch will throw a syntax error on mapping creation

D Documents with price field will be rejected on indexing

💡 Hint

Consider the data type mismatch impact on queries.

Mapping price as text means numeric range queries on price will fail or behave incorrectly.

📝 Syntax

advanced

Which option correctly creates an index with a keyword field?

Choose the correct JSON to create an Elasticsearch index with a category field of type keyword.

A { "mappings": { "properties": { "category": { "type": "keyword" } } } }

B { "mappings": { "properties": { "category": "keyword" } } }

C { "mappings": { "fields": { "category": { "type": "keyword" } } } }

D { "mapping": { "category": { "type": "keyword" } } }

💡 Hint

Check the correct key names for mappings and properties.

The correct structure uses mappings with properties containing the field name and its type.

🚀 Application

expert

How many shards will an index have after this creation command?

You create an Elasticsearch index with this command:

PUT /my_index
{
  "settings": {
    "number_of_shards": 3,
    "number_of_replicas": 2
  }
}

How many primary shards and total shards will this index have?

A 5 primary shards and 10 total shards

B 3 primary shards and 9 total shards

C 3 primary shards and 6 total shards

D 1 primary shard and 3 total shards

💡 Hint

Total shards = primary shards + (primary shards × replicas).

With 3 primary shards and 2 replicas each, total shards = 3 + (3×2) = 9 shards. But replicas are copies, so total shards = 3 primary + 6 replicas = 9 total shards.

Practice

1. Why do Elasticsearch indexes organize data?

easy

A. To slow down data retrieval

B. To store data in random order

C. To make searching fast and efficient

D. To delete data automatically

Solution

1. Step 1: Understand the purpose of indexes

   Indexes are designed to arrange data so that searching can be done quickly and easily.

2. Step 2: Compare options with the purpose

   Only To make searching fast and efficient matches the purpose of indexes; others describe incorrect behaviors.

3. Final Answer:

   To make searching fast and efficient -> Option C

4. Quick Check:

   Indexes speed up search = A [OK]

Hint: Indexes speed up search by organizing data [OK]

Common Mistakes:

• Thinking indexes slow down search
• Believing indexes store data randomly
• Assuming indexes delete data automatically

2. Which of the following is the correct way to create an index in Elasticsearch?

easy

A. PUT /my_index

B. GET /my_index

C. DELETE /my_index

D. POST /my_index/_search

Solution

1. Step 1: Identify the HTTP method for creating an index

   Creating an index uses the PUT method with the index name.

2. Step 2: Match the correct syntax

   PUT /my_index is the correct syntax; others perform different actions.

3. Final Answer:

   PUT /my_index -> Option A

4. Quick Check:

   PUT creates index = D [OK]

Hint: Use PUT to create an index in Elasticsearch [OK]

Common Mistakes:

• Using GET to create an index
• Confusing DELETE with creation
• Using POST for index creation instead of search

3. Given this Elasticsearch query on an index, what does it do?

{"query": {"match": {"title": "Elasticsearch"}}}

medium

A. Updates documents with title 'Elasticsearch'

B. Finds documents where the title contains 'Elasticsearch'

C. Deletes documents with title 'Elasticsearch'

D. Creates a new document with title 'Elasticsearch'

Solution

1. Step 1: Understand the query type

   The query uses 'match' which searches for documents matching the given text in the specified field.

2. Step 2: Interpret the query action

   This query finds documents where the 'title' field contains the word 'Elasticsearch'.

3. Final Answer:

   Finds documents where the title contains 'Elasticsearch' -> Option B

4. Quick Check:

   Match query searches text = C [OK]

Hint: Match queries find documents containing the text [OK]

Common Mistakes:

• Thinking match deletes or updates documents
• Confusing match with document creation
• Assuming match returns all documents

4. You tried to create an index with this command:

POST /my_index

Why might this cause an error?

medium

A. The command should be GET instead

B. The index name is missing

C. POST is only for searching

D. POST is not used to create indexes; PUT is required

Solution

1. Step 1: Recall correct HTTP method for index creation

   Creating an index requires the PUT method, not POST.

2. Step 2: Analyze the command used

   Using POST /my_index tries to create but is invalid syntax, causing an error.

3. Final Answer:

   POST is not used to create indexes; PUT is required -> Option D

4. Quick Check:

   PUT creates index, POST does not = A [OK]

Hint: Use PUT, not POST, to create indexes [OK]

Common Mistakes:

• Using POST instead of PUT for index creation
• Thinking POST is for creating indexes
• Confusing GET with creation commands

5. You want to speed up searches on a text field by controlling how data is saved. Which Elasticsearch feature helps organize data for this purpose?

hard

A. Mappings to define field types and analyzers

B. Deleting old indexes regularly

C. Using GET requests to fetch data

D. Adding more shards without mappings

Solution

1. Step 1: Understand how data organization affects search speed

   Settings and mappings control how data is stored and indexed, affecting search performance.

2. Step 2: Identify the feature that controls field types and analyzers

   Mappings define field types and analyzers, organizing data for efficient searching.

3. Final Answer:

   Mappings to define field types and analyzers -> Option A

4. Quick Check:

   Mappings organize data for fast search = B [OK]

Hint: Use mappings to organize data for faster search [OK]

Common Mistakes:

• Thinking deleting indexes speeds up search
• Confusing GET requests with data organization
• Believing shards alone improve search without mappings