[
https://issues.apache.org/jira/browse/CASSANDRA-14724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16617691#comment-16617691
]
Benedict commented on CASSANDRA-14724:
--------------------------------------
Ah, yes, so it will.
So I guess the only question remaining is if your concept of 'an hour' is
consistent with how other date libraries interpret the concept of an hour
across a DST boundary. It seems reasonable to me that they might, and either
way I guess we can leave this until DST is implemented (if ever).
The original scope of this ticket is clearly not addressable since none of our
libraries handle leapseconds, anyway, so I'll close as Not a Problem.
> Duration addition to Date/Timestamp is broken for leapseconds
> -------------------------------------------------------------
>
> Key: CASSANDRA-14724
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14724
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Benedict
> Assignee: Benjamin Lerer
> Priority: Major
> Labels: correctness
>
> Hours, Minutes and Seconds are not always of the same duration; it varies
> when they cross a leap second (or DST boundary). When we add durations to
> instants, we do not account for this (as we have by then lost the necessary
> information). Duration should take (and store) all components of time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
