You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Paulo Motta (JIRA)" <ji...@apache.org> on 2018/02/11 13:47:00 UTC

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

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

Paulo Motta commented on CASSANDRA-14227:
-----------------------------------------

[~VincentWhite] feel free to add your PoC patch from CASSANDRA-14092. :)

> Extend maximum expiration date
> ------------------------------
>
>                 Key: CASSANDRA-14227
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14227
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local Write-Read Paths
>            Reporter: Paulo Motta
>            Priority: Major
>
> 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
(v7.6.3#76005)

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