[ 
https://issues.apache.org/jira/browse/CASSANDRA-14092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16345733#comment-16345733
 ] 

Paulo Motta commented on CASSANDRA-14092:
-----------------------------------------

bq. Whether we should allow this resurrection is IMO highly questionable, not 
knowing what decisions have been taken outside of the database based on that 
data not being present/visible. My preference would be for gone data to stay 
gone, with another -D flag to turn on post-insert capping of the expiration 
date.

I don't expect us to take longer than a few weeks (at worst a couple of months) 
to come up with a permanent solution for this, our goal here is to prevent 
users from inadvertedly losing data in the time frame where the permanent fix 
is not available. People that detect that data have gone missing without 
issuing a deletion, will be aware of these issues and will likely take 
additional measures to remediate it - like reducing the TTL or update their 
application to correctly handle the data in the affected time period. I 
personally find it highly unlikely that this scenario will be a problem in 
practice,  as long we properly document and communicate the problem on 
NEWS.txt, users that were affected and care about their data will likely take 
additional measure to recover their state. 

> 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to