Object and nested types in Elasticsearch - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define an object type field named 'user' in the mapping.

Elasticsearch

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

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

Aobject

Bnested

Ckeyword

Dtext

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'nested' instead of 'object' when no nested querying is needed.

The 'object' type is used to define a JSON object field in Elasticsearch mapping.

2fill in blank

medium

Complete the code to define a nested type field named 'comments' in the mapping.

Elasticsearch

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

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

Aobject

Bnested

Ctext

Dkeyword

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'object' type when nested querying is required.

The 'nested' type allows arrays of objects to be queried independently in Elasticsearch.

3fill in blank

hard

Fix the error in the mapping by completing the type for the 'address' field.

Elasticsearch

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

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

Aobject

Btext

Cnested

Dkeyword

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'text' or 'keyword' for a complex object field.

The 'address' field is a JSON object, so it should be of type 'object' to hold subfields.

4fill in blank

hard

Fill both blanks to define a nested field 'orders' with a subfield 'date' of type 'date'.

Elasticsearch

{
  "mappings": {
    "properties": {
      "orders": {
        "type": "[1]",
        "properties": {
          "date": {
            "type": "[2]"
          }
        }
      }
    }
  }
}

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

Anested

Bobject

Cdate

Dtext

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'object' instead of 'nested' for 'orders'.

Using 'text' instead of 'date' for the 'date' field.

The 'orders' field is nested, and its 'date' subfield should be of type 'date' for date values.

5fill in blank

hard

Fill all three blanks to define an object field 'profile' with a nested field 'activities' having a 'type' subfield of keyword type.

Elasticsearch

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

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

Aobject

Bnested

Ckeyword

Dtext

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'nested' for 'profile' instead of 'object'.

Using 'text' instead of 'keyword' for the 'type' subfield.

'profile' is an object field, 'activities' is nested, and its 'type' subfield is keyword for exact matching.