[
https://issues.apache.org/jira/browse/CASSANDRA-17372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17490578#comment-17490578
]
Benedict Elliott Smith commented on CASSANDRA-17372:
----------------------------------------------------
bq. can you elaborate on why repair state is relevant here?
Honestly I didn't think it through before sending, I just included it as
expiring unrepaired data can lead to problems with tombstones. Since this
expiration will be applied in a blanket fashion that mightn't be an issue.
bq. I think we can make this a little safer by exposing some cluster-level
metadata about the state of TTL change and prevent a new TTL change if there is
still data not honoring the current TTL.
I'd personally be inclined to keep it simple, and just document it. Any
distributed mechanism for enforcing this will be more difficult to get right
than it's worth (particularly in ongoing maintenance).
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
