Date field types in Elasticsearch - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a date field in Elasticsearch mapping.

Elasticsearch

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

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

Akeyword

Bdate

Ctext

Dinteger

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'text' or 'keyword' instead of 'date' for date fields.

The date type is used to store date fields in Elasticsearch mappings.

2fill in blank

medium

Complete the code to specify a custom date format in the mapping.

Elasticsearch

{
  "mappings": {
    "properties": {
      "event_date": {
        "type": "date",
        "format": "[1]"
      }
    }
  }
}

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

Akeyword

Btext

Cyyyy-MM-dd HH:mm:ss

Dinteger

Attempts:

3 left

💡 Hint

Common Mistakes

Using data types like 'integer' or 'text' as the format value.

The format property defines the date pattern Elasticsearch expects, such as yyyy-MM-dd HH:mm:ss.

3fill in blank

hard

Fix the error in the date format specification.

Elasticsearch

{
  "mappings": {
    "properties": {
      "publish_date": {
        "type": "date",
        "format": "[1]"
      }
    }
  }
}

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

Ayyyy/MM/dd HH:mm:ss

Byyyy-MM-dd HH:mm:ssZ

Cyyyy-MM-dd HH:mm:ss

Dyyyy-MM-dd'T'HH:mm:ssZ

Attempts:

3 left

💡 Hint

Common Mistakes

Omitting the 'T' separator or timezone indicator in the format.

The correct ISO 8601 date format with timezone is yyyy-MM-dd'T'HH:mm:ssZ, which Elasticsearch expects for date fields with timezone.

4fill in blank

hard

Fill both blanks to create a mapping with a date field that accepts multiple formats.

Elasticsearch

{
  "mappings": {
    "properties": {
      "start_date": {
        "type": "date",
        "format": "[1]||[2]"
      }
    }
  }
}

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

Ayyyy-MM-dd

Bepoch_millis

Ctext

Dinteger

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid formats like 'text' or 'integer' as date formats.

Elasticsearch allows multiple date formats separated by ||. Here, yyyy-MM-dd and epoch_millis are valid formats.

5fill in blank

hard

Fill all three blanks to define a date field with a custom format, ignore malformed dates, and store dates as long.

Elasticsearch

{
  "mappings": {
    "properties": {
      "log_date": {
        "type": "date",
        "format": "[1]",
        "ignore_malformed": [2],
        "store": [3]
      }
    }
  }
}

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

Ayyyy-MM-dd HH:mm:ss

Btrue

Cfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using strings instead of booleans for ignore_malformed or store.

Incorrect date format strings.

The format defines the date pattern, ignore_malformed set to true skips bad dates, and store set to true stores the field separately for faster retrieval.