[
https://issues.apache.org/jira/browse/CASSANDRA-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251966#comment-13251966
]
Kirk True edited comment on CASSANDRA-3974 at 4/11/12 9:57 PM:
---------------------------------------------------------------
In the initial patch, I had made changes to both
{{UpdateStatement.addToMutation}} and {{ColumnFamily.addColumn}} to use the
larger of the column's TTL or the column family default TTL. I tested against
the {{cassandra-cli}} and {{cqlsh}} tools and both show the default TTL being
used if none is specified.
This is all to say that it _looks_ like both the Thrift and CQL paths are
working as expected. Perhaps it's high time I found the unit tests and added
some...
was (Author: kirktrue):
I made changes to both {{UpdateStatement.addToMutation}} and
{{ColumnFamily.addColumn}} to use the larger of the column's TTL or the column
family default TTL. I tested against the {{cassandra-cli}} and {{cqlsh}} tools
and both show the default TTL being used if none is specified.
This is all to say that it _looks_ like both the Thrift and CQL paths are
working as expected. Perhaps it's high time I found the unit tests and added
some...
> Per-CF TTL
> ----------
>
> Key: CASSANDRA-3974
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3974
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jonathan Ellis
> Assignee: Kirk True
> Priority: Minor
> Fix For: 1.2
>
> Attachments: trunk-3974.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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
