[
https://issues.apache.org/jira/browse/CASSANDRA-9672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616827#comment-14616827
]
Paulo Motta commented on CASSANDRA-9672:
----------------------------------------
Would this allow changing the default ttl on a table and enforcing it on
previously inserted data? This would be a desireable feature, since it's quite
common to come up with a initial TTL value, and then decide to change it for
whatever reason. Currently, in order to enforce a new TTL you have to reinsert
all the data, which is a pain for very large datasets, and it's quite a common
use case.
> Provide a per-table param that would force default ttl on all updates
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-9672
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9672
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Aleksey Yeschenko
> Priority: Minor
>
> Many users have tables that rely on TTL entirely - no deletes, and only fixed
> TTL value.
> The way that default ttl works now, we only apply it if none is specified.
> We should provide an option that would *enforce* the specified TTL. Not
> allowing ttl-less {{INSERT}} or {{UPDATE}}, not allowing ttl that's lower or
> higher than the default ttl, and not allowing deletes.
> That option when enabled ({{force_default_ttl}}) should allow us to drop more
> tables during compaction and do so cheaper. Would also allow the DBAs to
> enforce the constraint in a guaranteed manner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
