Date nanoseconds field typeedit

This data type is an addition to the date data type. However there is an important distinction between the two. The existing date data type stores dates in millisecond resolution. The date_nanos data type stores dates in nanosecond resolution, which limits its range of dates from roughly 1970 to 2262, as dates are still stored as a long representing nanoseconds since the epoch.

Queries on nanoseconds are internally converted to range queries on this long representation, and the result of aggregations and stored fields is converted back to a string depending on the date format that is associated with the field.

Date formats can be customised, but if no format is specified then it uses the default:


This means that it will accept dates with optional timestamps, which conform to the formats supported by strict_date_optional_time including up to nine second fractionals or milliseconds-since-the-epoch (thus losing precision on the nano second part). Using strict_date_optional_time will format the result up to only three second fractionals. To print and parse up to nine digits of resolution, use strict_date_optional_time_nanos.

For instance:

PUT my-index-000001?include_type_name=true
  "mappings": {
    "_doc": {
      "properties": {
        "date": {
          "type": "date_nanos" 

PUT my-index-000001/_bulk?refresh
{ "index" : { "_id" : "1" } }
{ "date": "2015-01-01" } 
{ "index" : { "_id" : "2" } }
{ "date": "2015-01-01T12:10:30.123456789Z" } 
{ "index" : { "_id" : "3" } }
{ "date": 1420070400000 } 

GET my-index-000001/_search
  "sort": { "date": "asc"}, 
  "runtime_mappings": {
    "date_has_nanos": {
      "type": "boolean",
      "script": "emit(doc['date'].value.nano != 0)" 
  "fields": [
      "field": "date",
      "format": "strict_date_optional_time_nanos" 
      "field": "date_has_nanos"

The date field uses the default format.

This document uses a plain date.

This document includes a time.

This document uses milliseconds-since-the-epoch.

Note that the sort values that are returned are all in nanoseconds-since-the-epoch.

Use .nano in scripts to return the nanosecond component of the date.

You can specify the format when fetching data using the fields parameter. Use strict_date_optional_time_nanos or you’ll get a rounded result.

You can also specify multiple date formats separated by ||. The same mapping parameters than with the date field can be used.

Date nanoseconds will accept numbers with a decimal point like {"date": 1618249875.123456} but there are some cases (#70085) where we’ll lose precision on those dates so should avoid them.


Aggregations are still on millisecond resolution, even when using a date_nanos field. This limitation also affects transforms.