[
https://issues.apache.org/jira/browse/CASSANDRA-14227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17636510#comment-17636510
]
Berenguer Blasi edited comment on CASSANDRA-14227 at 11/21/22 7:54 AM:
-----------------------------------------------------------------------
After some further perf testing we've found out there is a 3% disk size
increase hit we've like to avoid as discussed in the
[ML|https://lists.apache.org/thread/fyf2d9jlrsor3hmz46qn282o5goooowd]. We're
going to experiment and POC a bit a uint encoding to get rid of that and any
extra flushes as well.
was (Author: bereng):
After some further perf testing we've found out there is a 3% disk size
increase hit we've like to avoid as discussed in the
[ML|https://lists.apache.org/thread/fyf2d9jlrsor3hmz46qn282o5goooowd]. We're
going to experiment and POC a bit a unit encoding to get rid of that and any
extra flushes as well.
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
