honeymoose
/
OpenSearch
mirror of https://github.com/honeymoose/OpenSearch.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Docs: Fixed date format default option

This commit is contained in:
Clinton Gormley 2015-08-06 19:05:09 +02:00
parent 08687dfa3d
commit 0eb2ab915d
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/reference/mapping/types/date.asciidoc
View File

@ -3,7 +3,7 @@
JSON doesn't have a date datatype, so dates in Elasticsearch can either be:
* strings containing formatted dates, e.g. `¨2015-01-01¨` or `¨2015/01/01 12:10:30`.
* strings containing formatted dates, e.g. `"2015-01-01"` or `"2015/01/01 12:10:30"`.
* a long number representing _milliseconds-since-the-epoch_.
* an integer representing _seconds-since-the-epoch_.
@ -11,9 +11,13 @@ Internally, dates are converted to UTC (if the time-zone is specified) and
stored as a long number representing milliseconds-since-the-epoch.
Date formats can be customised, but if no `format` is specified then it uses
the default: `strictDateOptionalTime||epoch_millis`. This means that it will
accept dates with optional timestamps, which conform to the formats supported
by <<strict-date-time,`strictDateOptionalTime`>> or milliseconds-since-the-epoch.
the default:
"strict_date_optional_time||epoch_millis"
This means that it will accept dates with optional timestamps, which conform
to the formats supported by <<strict-date-time,`strict_date_optional_time`>>
or milliseconds-since-the-epoch.
For instance:
@ -99,7 +103,7 @@ The following parameters are accepted by `date` fields:
<<mapping-date-format,`format`>>::
The date format(s) that can be parsed. Defaults to
`epoch_millis||strictDateOptionalTime`.
`strict_date_optional_time||epoch_millis`.
<<ignore-malformed,`ignore_malformed`>>::