Date field types in Elasticsearch - Step-by-Step Execution

Concept Flow - Date field types

Define mapping with date field

↓

Index document with date value

↓

Elasticsearch parses date

↓

Stores date as milliseconds since epoch

↓

Date queries use stored format

↓

Return matching documents

This flow shows how Elasticsearch handles date fields: defining the field, indexing documents, parsing dates, storing them internally, and querying.

Execution Sample

Elasticsearch

PUT my_index
{
  "mappings": {
    "properties": {
      "created_at": { "type": "date" }
    }
  }
}

PUT my_index/_doc/1
{
  "created_at": "2024-06-01T12:00:00Z"
}

Defines an index with a date field and indexes a document with an ISO 8601 date string.

Execution Table

Step	Action	Input/Condition	Result/Output
1	Define index mapping	Field 'created_at' type=date	Mapping stored with date field type
2	Index document	created_at='2024-06-01T12:00:00Z'	Date string accepted
3	Parse date	Parse '2024-06-01T12:00:00Z'	Parsed to milliseconds since epoch (e.g. 1717243200000)
4	Store date	Store parsed milliseconds	Date stored internally as long integer
5	Query date	Search for documents with date range	Documents with matching date returned
6	Exit	No more documents	Index ready for date queries

💡 All steps complete; date field indexed and ready for queries

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
created_at	undefined	"2024-06-01T12:00:00Z"	1717243200000 (ms)	1717243200000 (stored)	1717243200000 (stored)

Key Moments - 3 Insights

Why does Elasticsearch store dates as numbers instead of strings?

Elasticsearch converts date strings to milliseconds since epoch (see Step 3 in execution_table) to enable fast range queries and sorting.

What happens if the date format in the document doesn't match the expected format?

Elasticsearch will fail to parse the date and reject the document or field update (not shown in this trace but parsing is critical at Step 3).

Can you store dates in formats other than ISO 8601?

Yes, but you must specify the format in the mapping so Elasticsearch can parse it correctly during Step 3.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'created_at' after Step 3?

A Milliseconds since epoch (e.g. 1717243200000)

B The original date string '2024-06-01T12:00:00Z'

C A formatted date string like 'June 1, 2024'

D Undefined

💡 Hint

Check the 'Result/Output' column in Step 3 of the execution_table.

At which step does Elasticsearch store the date internally as a number?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look for the step where the date is 'stored internally as long integer' in the execution_table.

If you index a document with a date in a custom format without updating the mapping, what will happen?

A Elasticsearch will parse it correctly anyway

B The document will be rejected due to parsing error

C The date will be stored as a string

D The date will be ignored silently

💡 Hint

Refer to the key_moments section about date format parsing and errors.

Concept Snapshot

Date field types in Elasticsearch:
- Define date fields in mapping with "type": "date"
- Index date strings (default ISO 8601)
- Elasticsearch parses dates to milliseconds since epoch
- Stores dates as long integers internally
- Enables fast date range queries and sorting
- Custom formats require mapping update

Full Transcript

This visual trace shows how Elasticsearch handles date field types. First, you define a mapping with a date field. Then, when you index a document with a date string, Elasticsearch parses that string into milliseconds since the epoch (January 1, 1970). It stores this number internally for efficient searching and sorting. Queries on date fields use this stored format to quickly find matching documents. If the date format does not match the expected format, Elasticsearch will reject the document. Custom date formats can be supported by specifying them in the mapping. This process ensures dates are handled consistently and efficiently.