honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-03-28 02:48:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

[Docs] Explain incomplete dates in range queries ()

Browse Source 
The current documentation isn't very clear about how incomplete dates are
treated when specifying custom formats in a `range` query. This change adds a
note explaining how missing month or year coordinates translate to dates that
have the missings slots filled with unix time start date (1970-01-01)

Closes
This commit is contained in:
Christoph Büscher 2018-05-24 11:20:00 +02:00 committed by GitHub
parent aafcd85f50
commit 3f78b3f5e1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions

6
docs/reference/query-dsl/range-query.asciidoc

@ -109,6 +109,12 @@ GET _search
--------------------------------------------------
// CONSOLE
Note that if the date misses some of the year, month and day coordinates, the
missing parts are filled with the start of
https://en.wikipedia.org/wiki/Unix_time[unix time], which is January 1st, 1970.
This means, that when e.g. specifying `dd` as the format, a value like `"gte" : 10`
will translate to `1970-01-10T00:00:00.000Z`.
===== Time zone in range queries
Dates can be converted from another timezone to UTC either by specifying the