Missing documentation of formats on dates in range queries #30634
Labels
>docs
General docs changes
:Search/Search
Search-related issues that do not fall into other categories
Comments
|
Pinging @elastic/es-search-aggs |
colings86
added
the
:Search/Search
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
May 17, 2018
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 elastic#30634
cbuescher
pushed a commit
that referenced
this issue
May 24, 2018
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 #30634
cbuescher
pushed a commit
that referenced
this issue
May 24, 2018
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 #30634
cbuescher
pushed a commit
that referenced
this issue
May 24, 2018
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 #30634
cbuescher
pushed a commit
that referenced
this issue
May 24, 2018
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 #30634
cbuescher
pushed a commit
that referenced
this issue
May 24, 2018
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 #30634
cbuescher
pushed a commit
that referenced
this issue
May 24, 2018
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 #30634
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Elasticsearch version (
bin/elasticsearch --version):n/aPlugins installed: n/a
JVM version (
java -version): n/aOS version (
uname -aif on a Unix-like system): n/aDescription of the problem including expected versus actual behavior:
According to Elastic, formats on range queries need to resolve to a specific date. The documentation does not mention this.
Someone who knows how formats on dates in range queries work needs to update the documentation. It appears to me that the format always needs to include the year, and can only include finer grained periods if all of the coarser periods are specified.
Steps to reproduce: n/a
Provide logs (if relevant): n/a
The text was updated successfully, but these errors were encountered: