You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Berenguer Blasi (Jira)" <ji...@apache.org> on 2023/05/26 09:52:00 UTC

[jira] [Updated] (CASSANDRA-14227) Extend maximum expiration date

     [ https://issues.apache.org/jira/browse/CASSANDRA-14227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Berenguer Blasi updated CASSANDRA-14227:
----------------------------------------
    Attachment: C14227 Perf check 2023.05.26.pdf

> 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: 5.x
>
>         Attachments: C14227 Perf check 2023.03.21.pdf, C14227 Perf check 2023.05.26.pdf, 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org