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

Benjamin Lerer commented on CASSANDRA-14227:
--------------------------------------------

I think, that I am misunderstanding what we call downgradability. What you 
propose is some kind of feature flag that delay the problem, no? If a problem 
occurs once we switch to the new sstable format then we cannot downgrade 
anymore.

> Extend maximum expiration date
> ------------------------------
>
>                 Key: CASSANDRA-14227
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14227
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Legacy/Local Write-Read Paths
>            Reporter: Paulo Motta (Deprecated)
>            Assignee: Berenguer Blasi
>            Priority: Urgent
>             Fix For: 4.x
>
>         Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, 
> screenshot-4.png, unnamed-1.png
>
>
> The maximum expiration timestamp that can be represented by the storage 
> engine is
> 2038-01-19T03:14:06+00:00 due to the encoding of {{localExpirationTime}} as 
> an int32.
> On CASSANDRA-14092 we added an overflow policy which rejects requests with 
> expiration above the maximum date as a temporary measure, but we should 
> remove this limitation by updating the storage engine to support at least the 
> maximum allowed TTL of 20 years.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to