Clarify using time_zone and date math in range query #40655
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Currently, the docs correctly state that using `now` in range queries will not be affected by the `time_zone` parameter. However, using date math roundings like e.g. `now\d` will be affected by the `time_zone`. Adding this example because it seems to be a frequently asked question and source of confusion. Relates to elastic#40581
cbuescher
added
>docs
|
Pinging @elastic/es-search |
jtibshirani
approved these changes
Mar 29, 2019
cbuescher
pushed a commit
that referenced
this pull request
Mar 29, 2019
Currently, the docs correctly state that using `now` in range queries will not be affected by the `time_zone` parameter. However, using date math roundings like e.g. `now\d` will be affected by the `time_zone`. Adding this example because it seems to be a frequently asked question and source of confusion. Relates to #40581
cbuescher
pushed a commit
that referenced
this pull request
Mar 29, 2019
Currently, the docs correctly state that using `now` in range queries will not be affected by the `time_zone` parameter. However, using date math roundings like e.g. `now\d` will be affected by the `time_zone`. Adding this example because it seems to be a frequently asked question and source of confusion. Relates to #40581
cbuescher
pushed a commit
that referenced
this pull request
Mar 29, 2019
Currently, the docs correctly state that using `now` in range queries will not be affected by the `time_zone` parameter. However, using date math roundings like e.g. `now\d` will be affected by the `time_zone`. Adding this example because it seems to be a frequently asked question and source of confusion. Relates to #40581
jasontedor
added a commit
to jasontedor/elasticsearch
that referenced
this pull request
Apr 1, 2019
* elastic/7.0: [TEST] Mute WebhookHttpsIntegrationTests.testHttps [DOCS] Add 'time value' links to several monitor settings (elastic#40633) (elastic#40687) Do not perform cleanup if Manifest write fails with dirty exception (elastic#40519) Remove mention of soft deletes from getting started (elastic#40668) Fix bug in detecting use of bundled JDK on macOS Reindex conflicts clarification (docs) (elastic#40442) SQL: [Tests] Enable integration tests for fixed issues (elastic#40664) Add information about the default sort mode (elastic#40657) SQL: [Docs] Fix example for CURDATE SQL: [Docs] Fix doc errors regarding CURRENT_DATE. (elastic#40649) Clarify using time_zone and date math in range query (elastic#40655) Add notice for bundled jdk (elastic#40576) disable kerberos test until kerberos fixture is working again [DOCS] Use "source" instead of "inline" in ML docs (elastic#40635) Unmute and fix testSubParserArray (elastic#40626) Geo Point parse error fix (elastic#40447) Increase suite timeout to 30 minutes for docs tests (elastic#40521) Fix repository-hdfs when no docker and unnecesary fixture Avoid building hdfs-fixure use an image that works instead
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the docs correctly state that using
nowin range queries will notbe affected by the
time_zoneparameter. However, using date math roundingslike e.g.
now\dwill be affected by thetime_zone. Adding this examplebecause it seems to be a frequently asked question and source of confusion.
Relates to #40581