You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict Elliott Smith (Jira)" <ji...@apache.org> on 2022/02/10 21:02:00 UTC

[jira] [Comment Edited] (CASSANDRA-17372) Dynamic Table TTL

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

Benedict Elliott Smith edited comment on CASSANDRA-17372 at 2/10/22, 9:01 PM:
------------------------------------------------------------------------------

Internally we refer to TTLs as having an expiration time, and I’m sure we have in documentation and blog posts and the like. I think that having a proliferation of feature names is sometimes more confusing and we should just call this table-level TTL. If we currently call the table level default for cell level TTLs a table level TTL then we perhaps have a problem, and can either introduce a flag for how this functions or perhaps rename it in our parlance to default TTL.


was (Author: benedict):
Internally we refer to TTLs as having an expiration time, and I’m sure we have in documentation and blog posts and the like. I think that having a proliferation of feature names is sometimes more confusing and we should just call this table-level TTL

> Dynamic Table TTL
> -----------------
>
>                 Key: CASSANDRA-17372
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17372
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL/Semantics
>            Reporter: Paulo Motta
>            Priority: Normal
>
> One limitation of the {{default_time_to_live}} option is that it only applies to newly inserted data so an expensive migration is required when altering the table-level TTL, which is not an uncommon request due to changes in retention policies.
> This seems to have been a deliberate design decision when adding the Table TTL feature on CASSANDRA-3974, due to the reasons stated [on this comment|https://issues.apache.org/jira/browse/CASSANDRA-3974?focusedCommentId=13427314&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13427314] so we should revisit and potentially address these concerns.
> I would like to explore supporting dynamic TTL, which would reflect any updates to the table-level {{default_time_to_live}} immediately to all table data.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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