[
https://issues.apache.org/jira/browse/CASSANDRA-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16347924#comment-16347924
]
Kurt Greaves edited comment on CASSANDRA-14092 at 2/1/18 2:35 AM:
------------------------------------------------------------------
I don't think it's a good idea not to fix the data. That's incrementally going
to break more and more applications as we get closer to 2038. We should be
fixing the data, making it very clear that we are in fact fixing the data
(client and server warnings) and advertising heavily on the website/ML/NEWS.txt
for people to get off affected versions.
was (Author: kurtg):
I don't think it's a good idea not to fix the data. That's incrementally going
to break more and more applications as we get closer to 2038. We should be
fixing the data, making it very clear that we are in fact fixing the data
(client and server warnings) and advertising heavily on the website/ML/NEWS.txt
for people to get off affected minor versions.
> Max ttl of 20 years will overflow localDeletionTime
> ---------------------------------------------------
>
> Key: CASSANDRA-14092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14092
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Paulo Motta
> Assignee: Paulo Motta
> Priority: Blocker
> Fix For: 2.1.20, 2.2.12, 3.0.16, 3.11.2
>
>
> CASSANDRA-4771 added a max value of 20 years for ttl to protect against [year
> 2038 overflow bug|https://en.wikipedia.org/wiki/Year_2038_problem] for
> {{localDeletionTime}}.
> It turns out that next year the {{localDeletionTime}} will start overflowing
> with the maximum ttl of 20 years ({{System.currentTimeMillis() + ttl(20
> years) > Integer.MAX_VALUE}}), so we should remove this limitation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
