Date field types in Elasticsearch - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the date field type in Elasticsearch?

The date field type stores dates and times in Elasticsearch, allowing efficient range queries, sorting, and date math operations.

beginner

How does Elasticsearch interpret date formats by default?

By default, Elasticsearch expects dates in the ISO 8601 format, like yyyy-MM-dd'T'HH:mm:ssZ, but you can customize the format using the format parameter.

intermediate

What is the role of the format parameter in a date field mapping?

The format parameter tells Elasticsearch how to parse date strings. It can accept multiple formats separated by || to handle different date styles in the same field.

intermediate

Explain the difference between storing dates as strings vs. using the date field type.

Storing dates as strings treats them as plain text, so you can't do date math or range queries efficiently. Using the date field type stores them as timestamps, enabling fast date operations and sorting.

advanced

What happens if a date value does not match the specified format in Elasticsearch?

Elasticsearch will reject the document or field update with a parsing error because it cannot convert the value to a valid date according to the specified format.

Which default format does Elasticsearch expect for date fields?

A Unix timestamp in seconds

B RFC 2822

C MM/dd/yyyy

D ISO 8601

Elasticsearch expects ISO 8601 format by default, like 2023-06-01T12:00:00Z.

How can you allow multiple date formats for a single date field?

A Separate formats with <code>||</code> in the <code>format</code> parameter

B Use multiple <code>date</code> fields

C Elasticsearch does not support multiple formats

D Use a script to convert dates

You can list multiple formats separated by || in the format parameter.

What is a benefit of using the date field type over storing dates as strings?

A Supports date math and range queries

B Allows storing multiple dates in one field

C Consumes less disk space

D Faster text search

The date type enables date math and range queries, which strings do not.

If a date does not match the specified format, what happens?

A Elasticsearch stores it as null

B Elasticsearch throws a parsing error

C Elasticsearch converts it to the current date

D Elasticsearch ignores the field

Elasticsearch throws a parsing error and rejects the document or update.

Which of these is NOT a valid date format pattern in Elasticsearch?

A HH:mm:ss

B epoch_millis

C random_format

D yyyy-MM-dd

Only recognized date patterns or built-in formats like epoch_millis are valid.

Describe how to define a date field in Elasticsearch with multiple accepted date formats.

Think about how to tell Elasticsearch to accept different date styles in one field.

Explain why using the date field type is better than storing dates as strings in Elasticsearch.

Consider what operations you want to do with dates.

Practice

1. What is the primary purpose of a date field type in Elasticsearch?

easy

A. To store and query time and date information

B. To store large text documents

C. To perform mathematical calculations

D. To store binary data

Solution

1. Step 1: Understand the role of field types in Elasticsearch

   Field types define how data is stored and interpreted in Elasticsearch.

2. Step 2: Identify the function of the date field type

   The date field type specifically stores time and date information for searching and sorting.

3. Final Answer:

   To store and query time and date information -> Option A

4. Quick Check:

   Date field = store time/date [OK]

Hint: Date fields store time info, not text or numbers [OK]

Common Mistakes:

• Confusing date fields with text fields
• Thinking date fields store binary data
• Assuming date fields perform calculations

2. Which of the following is the correct way to define a date field with a custom format in an Elasticsearch mapping?

easy

A. {
"mappings": {
"properties": {
"created_at": {"type": "integer", "format": "yyyy-MM-dd"}
}
}
}

B. {
"mappings": {
"properties": {
"created_at": {"type": "date", "format": "yyyy-MM-dd HH:mm:ss"}
}
}
}

C. {
"mappings": {
"properties": {
"created_at": {"type": "date"}
}
}
}

D. {
"mappings": {
"properties": {
"created_at": {"type": "text", "format": "yyyy-MM-dd"}
}
}
}

Solution

1. Step 1: Check the field type for date

   The field must have type set to date to store dates.

2. Step 2: Verify the format property

   Custom date formats are specified with the format key inside the date field definition.

3. Final Answer:

   Mapping with type 'date' and format 'yyyy-MM-dd HH:mm:ss' -> Option B

4. Quick Check:

   Date type + format key = correct mapping [OK]

Hint: Date fields need type 'date' and format string [OK]

Common Mistakes:

• Using type 'text' or 'integer' for date fields
• Omitting the format when using custom date strings
• Placing format outside the date field definition

3. Given this Elasticsearch mapping and document, what will be the stored value for the event_date field?

{
  "mappings": {
    "properties": {
      "event_date": { "type": "date", "format": "yyyy/MM/dd" }
    }
  }
}

Document:
{
  "event_date": "2024/06/15"
}

medium

A. Error: Invalid date format

B. "2024/06/15"

C. "2024-06-15T00:00:00.000Z"

D. "15-06-2024"

Solution

1. Step 1: Understand the mapping format

   The mapping expects dates in the format "yyyy/MM/dd" which matches the document date "2024/06/15".

2. Step 2: Know how Elasticsearch stores dates internally

   Elasticsearch converts dates to ISO 8601 format with time and timezone, so it stores "2024-06-15T00:00:00.000Z".

3. Final Answer:

   "2024-06-15T00:00:00.000Z" -> Option C

4. Quick Check:

   Input format matches mapping, stored as ISO date [OK]

Hint: Input matches format, stored as ISO 8601 date [OK]

Common Mistakes:

• Expecting stored value to keep original format
• Thinking Elasticsearch stores raw string
• Confusing format mismatch errors

4. You defined a date field with format yyyy-MM-dd but indexing documents with dates like 2024/06/15 causes errors. What is the best fix?

medium

A. Change the mapping format to include yyyy/MM/dd

B. Convert all dates to yyyy-MM-dd before indexing

C. Change the field type to text

D. Remove the format from the mapping

Solution

1. Step 1: Identify the cause of the error

   The document dates use slashes / but the mapping expects dashes -, causing format mismatch errors.

2. Step 2: Fix the mapping to accept the document date format

   Update the mapping format to include yyyy/MM/dd so Elasticsearch can parse the input dates correctly.

3. Final Answer:

   Change the mapping format to include yyyy/MM/dd -> Option A

4. Quick Check:

   Mapping format must match input date format [OK]

Hint: Mapping format must match input date format exactly [OK]

Common Mistakes:

• Changing field type to text loses date features
• Removing format causes parsing errors if format differs
• Not updating mapping when input format changes

5. You want to index documents with multiple date fields: created_at in ISO format and due_date in dd-MM-yyyy format. How should you define the mapping to handle both correctly?

hard

A. {
"mappings": {
"properties": {
"created_at": { "type": "date", "format": "dd-MM-yyyy" },
"due_date": { "type": "date" }
}
}
}

B. {
"mappings": {
"properties": {
"created_at": { "type": "date", "format": "dd-MM-yyyy" },
"due_date": { "type": "date", "format": "dd-MM-yyyy" }
}
}
}

C. {
"mappings": {
"properties": {
"created_at": { "type": "text" },
"due_date": { "type": "text" }
}
}
}

D. {
"mappings": {
"properties": {
"created_at": { "type": "date" },
"due_date": { "type": "date", "format": "dd-MM-yyyy" }
}
}
}

Solution

1. Step 1: Understand the formats of each date field

   created_at uses ISO format (default), due_date uses custom dd-MM-yyyy format.

2. Step 2: Define mapping with correct formats per field

   Set created_at as date with default format, and due_date as date with format: dd-MM-yyyy.

3. Final Answer:

   Mapping with default date for created_at and custom format for due_date -> Option D

4. Quick Check:

   Each date field needs correct format in mapping [OK]

Hint: Set format per date field to match its input format [OK]

Common Mistakes:

• Using text type instead of date loses date features
• Applying wrong format to a field causes parsing errors
• Using same format for different date formats