[
https://issues.apache.org/jira/browse/CASSANDRA-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496334#comment-13496334
]
Jonathan Ellis commented on CASSANDRA-3974:
-------------------------------------------
If we use ttl <= 0 as a signal to use the default ttl in CF.addColumn, how do
we override the default to be "no ttl at all?" Should we treat
Integer.MAX_VALUE as "don't use the default, just give me a non-expiring
Column?"
Does UpdateStatement go through addColumn eventually? If so we are duplicating
code there. If not that makes me a bigger fan of centralizing this in a
factory method. (Guess we can leave the other constructors alone.)
> Per-CF TTL
> ----------
>
> Key: CASSANDRA-3974
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3974
> Project: Cassandra
> Issue Type: New Feature
> Affects Versions: 1.2.0 beta 1
> Reporter: Jonathan Ellis
> Assignee: Kirk True
> Priority: Minor
> Fix For: 1.2.0 rc1
>
> Attachments: trunk-3974.txt, trunk-3974v2.txt, trunk-3974v3.txt,
> trunk-3974v4.txt, trunk-3974v5.txt, trunk-3974v6.txt, trunk-3974v7.txt
>
>
> Per-CF TTL would allow compaction optimizations ("drop an entire sstable's
> worth of expired data") that we can't do with per-column.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
