[
https://issues.apache.org/jira/browse/CASSANDRA-9672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605484#comment-14605484
]
Aleksey Yeschenko commented on CASSANDRA-9672:
----------------------------------------------
Yeah, that could work as well.
That said, a forced single TTL strictness guarantees us that there no
overwrites of the same cells with a lower TTL ever happens, and that *should*
allow us to optimize harder.
We probably could/should provide several different options to hint the usage
patterns, with varying degrees of strictness.
> 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)
