Return date/time in UTC in JMX connector #5488
Merged
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.
Using server zone introduces ambiguity problem during DST change.
Presto engine has no problem representing and distinguishing
(point-in-time, zone)
pairs regardless of DST. However, due tohow they are formatted for the client, client can no longer distinguish
values within summer→winter DST change.
In the example below, rows with
increment
1 and 2 represent differentpoint in time, but are rendered the same for the client.