[Docs] Correct date rounding example for `range` query (#51524)

Looking into #50237 I realized that two of the examples given in the
documentation around date math rounding for range queries on date fields using
`gt` and `lt` is slightly off by a nanosecond. This PR changes this to the
bounds that are currently parsed using these parameters.
This commit is contained in:
Christoph Büscher 2020-04-06 17:02:38 +02:00
parent 816fec7187
commit def519ea70
1 changed files with 8 additions and 8 deletions

View File

@ -176,10 +176,10 @@ GET /_search
`gt`:: `gt`::
+ +
-- --
Rounds up to the lastest millisecond. Rounds up to the first millisecond not covered by the rounded date.
For example, `2014-11-18||/M` rounds up to `2014-11-30T23:59:59.999`, excluding For example, `2014-11-18||/M` rounds up to `2014-12-01T00:00:00.000`, excluding
the entire month. the entire month of November.
-- --
`gte`:: `gte`::
@ -187,23 +187,23 @@ the entire month.
-- --
Rounds down to the first millisecond. Rounds down to the first millisecond.
For example, `2014-11-18||/M` rounds down to `2014-11-01`, including For example, `2014-11-18||/M` rounds down to `2014-11-01T00:00:00.000`, including
the entire month. the entire month.
-- --
`lt`:: `lt`::
+ +
-- --
Rounds down to the first millisecond. Rounds down to the last millisecond before the rounded value.
For example, `2014-11-18||/M` rounds down to `2014-11-01`, excluding For example, `2014-11-18||/M` rounds down to `2014-10-31T23:59:59.999`, excluding
the entire month. the entire month of November.
-- --
`lte`:: `lte`::
+ +
-- --
Rounds up to the latest millisecond. Rounds up to the latest millisecond in the rounding interval.
For example, `2014-11-18||/M` rounds up to `2014-11-30T23:59:59.999`, including For example, `2014-11-18||/M` rounds up to `2014-11-30T23:59:59.999`, including
the entire month. the entire month.