Fix date_histogram issues during a timezone DST switch #8655
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
|
Merged, thanks! |
clintongormley
changed the title
clintongormley
added
>bug
v1.3.6
v1.4.1
v1.5.0
v2.0.0-beta1
:Analytics/Aggregations
clintongormley
changed the title
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.
The problem was in the difference between the two responses of the
preTz.getOffsetcall. To solve this I only call it once.The behaviour of
roundKeychanged that it is now returning the actual rounded timestamp rounded timestamp offsetted to UTC. The exact opposite is true forvalueForKeywhich used to accept the UTC offsetted timestamp but now needs to work on the normal timestamp.The tests for rounding are all passing, including the tests I added where the issue was shown.
Closes #8339
/cc @jpountz