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

Update format.asciidoc to describe strict_date_optional_time_nanos (#57527) (#58581) 

closes #57019
This commit is contained in:
Przemyslaw Gomulka 2020-06-26 09:02:08 +02:00 committed by GitHub
parent a524800b3e
commit 5149554709
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/reference/mapping/params/format.asciidoc
View File

@ -66,10 +66,17 @@ The following tables lists all the defaults ISO formats supported:
[[strict-date-time]]`date_optional_time` or `strict_date_optional_time`:: [[strict-date-time]]`date_optional_time` or `strict_date_optional_time`::
A generic ISO datetime parser where the date, in `year_month_day` format, is A generic ISO datetime parser, where the date must include the year at a minimum, and the time
mandatory and the time, separated by `T`, is optional. (separated by `T`), is optional.
Examples: `yyyy-MM-dd'T'HH:mm:ss.SSSZ` or `yyyy-MM-dd`. Examples: `yyyy-MM-dd'T'HH:mm:ss.SSSZ` or `yyyy-MM-dd`.
[[strict-date-time-nanos]]`strict_date_optional_time_nanos`::
A generic ISO datetime parser, where the date must include the year at a minimum, and the time
(separated by `T`), is optional. The fraction of a second
part has a nanosecond resolution.
Examples: `yyyy-MM-dd'T'HH:mm:ss.SSSSSSZ` or `yyyy-MM-dd`.
`basic_date`:: `basic_date`::
A basic formatter for a full date as four digit year, two digit month of A basic formatter for a full date as four digit year, two digit month of

5
docs/reference/mapping/types/date_nanos.asciidoc
View File

@ -24,7 +24,9 @@ This means that it will accept dates with optional timestamps, which conform
to the formats supported by to the formats supported by
<<strict-date-time,`strict_date_optional_time`>> including up to nine second <<strict-date-time,`strict_date_optional_time`>> including up to nine second
fractionals or milliseconds-since-the-epoch (thus losing precision on the fractionals or milliseconds-since-the-epoch (thus losing precision on the
nano second part). nano second part). Using <<strict-date-time,`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-time-nanos,`strict_date_optional_time_nanos`>>.
For instance: For instance:
@ -98,4 +100,3 @@ same mapping parameters than with the `date` field can be used.
Aggregations are still on millisecond resolution, even when using a `date_nanos` Aggregations are still on millisecond resolution, even when using a `date_nanos`
field. This limitation also affects <<transforms,{transforms}>>. field. This limitation also affects <<transforms,{transforms}>>.