[ https://issues.apache.org/jira/browse/CASSANDRA-14227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17450322#comment-17450322 ]
Spiros Ioannou edited comment on CASSANDRA-14227 at 11/29/21, 10:19 AM: ------------------------------------------------------------------------ This is a critical issue, that severely limits TTL functionality; the CAP_NOWARN workaround of CASSANDRA-14092 is already limiting our data lifecycle. I'm not sure why this is high-severity issue was not planned for 4.0, what's missing? was (Author: sivann): This is a critical issue, that severely limits TTL functionality and future design, the CAP_NOWARN workaround of CASSANDRA-14092 is already limiting our data lifecycle. I'm not sure why this is high-severity issue was not planned for 4.0, what's missing? > 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) > Priority: Urgent > > 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.1#820001) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org