Creating an index in Elasticsearch - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an index named "library".

Elasticsearch

{
  "[1]": "library"
}

Drag options to blanks, or click blank then click option'

Atype

Bid

Cname

Dindex

Attempts:

3 left

💡 Hint

Common Mistakes

Using "type" instead of "index"

Using "name" which is not recognized

Using "id" which is unrelated

The key to create an index in Elasticsearch is "index" which specifies the index name.

2fill in blank

medium

Complete the code to set the number of shards to 3 in the index settings.

Elasticsearch

{
  "settings": {
    "number_of_shards": [1]
  }
}

Drag options to blanks, or click blank then click option'

A"3"

B"three"

C3

Dshards

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the number in quotes making it a string

Using the word "three" instead of the number

Using an unrelated string like "shards"

The number of shards must be a number, so 3 without quotes is correct.

3fill in blank

hard

Fix the error in the mapping by completing the field type for "title".

Elasticsearch

{
  "mappings": {
    "properties": {
      "title": {
        "type": "[1]"
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Astring

Btext

Ckeyword

Dfield

Attempts:

3 left

💡 Hint

Common Mistakes

Using "string" which is not a valid type in recent Elasticsearch versions

Using "keyword" which is for exact matches, not full text

Using "field" which is invalid

"text" is the correct type for full-text searchable fields in Elasticsearch.

4fill in blank

hard

Fill both blanks to set the number of replicas to 2 and refresh interval to 1s.

Elasticsearch

{
  "settings": {
    "number_of_replicas": [1],
    "refresh_interval": "[2]"
  }
}

Drag options to blanks, or click blank then click option'

A2

B1s

C3

D5s

Attempts:

3 left

💡 Hint

Common Mistakes

Putting refresh interval as a number without quotes

Using wrong numbers for replicas

Using invalid time units

Number of replicas is a number (2), and refresh interval is a string with time unit ("1s").

5fill in blank

hard

Fill all three blanks to create a mapping for a "date" field named "publish_date" with format "yyyy-MM-dd".

Elasticsearch

{
  "mappings": {
    "properties": {
      "[1]": {
        "type": "[2]",
        "format": "[3]"
      }
    }
  }
}

Drag options to blanks, or click blank then click option'

Apublish_date

Bdate

Cyyyy-MM-dd

Dtext

Attempts:

3 left

💡 Hint

Common Mistakes

Using "text" as type instead of "date"

Using wrong format strings

Mixing field name and type

The field name is "publish_date", type is "date", and the format is "yyyy-MM-dd" for year-month-day.

Practice

1. What is the main purpose of creating an index in Elasticsearch?

easy

A. To encrypt data for security

B. To delete data permanently

C. To backup data automatically

D. To organize data for fast searching

Solution

1. Step 1: Understand the role of an index

   An index in Elasticsearch is like a folder that organizes documents to make searching fast and efficient.

2. Step 2: Compare options with index purpose

   Deleting, backing up, or encrypting data are not the main functions of an index.

3. Final Answer:

   To organize data for fast searching -> Option D

4. Quick Check:

   Index = Organize data for search [OK]

Hint: Index means organizing data for quick search [OK]

Common Mistakes:

• Confusing index with backup or encryption
• Thinking index deletes data
• Assuming index automatically secures data

2. Which is the correct syntax to create an index named products in Elasticsearch?

easy

A. PUT /products

B. POST /products

C. GET /products

D. DELETE /products

Solution

1. Step 1: Recall HTTP methods for index creation

   Elasticsearch uses the PUT method to create an index with a specific name.

2. Step 2: Match method with index name

   PUT /products correctly creates the index named 'products'. POST is used for adding documents, GET for retrieving, DELETE for removing.

3. Final Answer:

   PUT /products -> Option A

4. Quick Check:

   PUT creates index [OK]

Hint: Use PUT to create an index by name [OK]

Common Mistakes:

• Using POST instead of PUT for index creation
• Confusing GET with creation
• Trying DELETE to create index

3. Given this request to create an index:

{
  "settings": {"number_of_shards": 1},
  "mappings": {
    "properties": {
      "name": {"type": "text"},
      "price": {"type": "float"}
    }
  }
}

What will be the type of the price field in the index?

medium

A. keyword

B. float

C. integer

D. text

Solution

1. Step 1: Read the mapping for the price field

   The mapping defines "price" with "type": "float" which means it stores decimal numbers.

2. Step 2: Understand field types

   Float is a number with decimals, integer is whole number, text is for full text search, keyword is for exact matches.

3. Final Answer:

   float -> Option B

4. Quick Check:

   price type = float [OK]

Hint: Check mapping 'type' for field data type [OK]

Common Mistakes:

• Confusing float with integer
• Assuming text type for numbers
• Mixing keyword with numeric types

4. Identify the error in this index creation request:

PUT /library
{
  "settings": {
    "number_of_shards": "two"
  },
  "mappings": {
    "properties": {
      "title": {"type": "text"}
    }
  }
}

medium

A. number_of_shards should be a number, not a string

B. title field type should be keyword, not text

C. PUT method cannot be used to create index

D. Missing index name in URL

Solution

1. Step 1: Check the settings syntax

   number_of_shards must be a numeric value, but "two" is a string, causing an error.

2. Step 2: Validate other parts

   Field type 'text' is valid for title, PUT is correct method, index name 'library' is present.

3. Final Answer:

   number_of_shards should be a number, not a string -> Option A

4. Quick Check:

   number_of_shards = number [OK]

Hint: Settings values must match expected data types [OK]

Common Mistakes:

• Using string instead of number for shards
• Confusing field types for text fields
• Using wrong HTTP method for index creation

5. You want to create an index users with a field age that should only accept whole numbers and be searchable. Which mapping is correct?

hard

A. { "mappings": { "properties": { "age": { "type": "float" } } } }

B. { "mappings": { "properties": { "age": { "type": "text" } } } }

C. { "mappings": { "properties": { "age": { "type": "integer" } } } }

D. { "mappings": { "properties": { "age": { "type": "keyword" } } } }

Solution

1. Step 1: Understand the data type needed for age

   Age is a whole number, so integer type is appropriate to store numeric whole values.

2. Step 2: Check searchability and field types

   Text is for full text search, float allows decimals, keyword is for exact matches but not numeric operations.

3. Final Answer:

   { "mappings": { "properties": { "age": { "type": "integer" } } } } -> Option C

4. Quick Check:

   Whole number field = integer type [OK]

Hint: Use integer type for whole number searchable fields [OK]

Common Mistakes:

• Using text type for numeric fields
• Choosing float when decimals not needed
• Using keyword for numeric data